Re: [Xen-devel] [PATCH 3/4] xen/hvc: CheckHVM_PARAM_CONSOLE_[EVTCHN|PFN] for correctness.

From: Konrad Rzeszutek Wilk
Date: Thu May 24 2012 - 14:30:36 EST

Next message: Konrad Rzeszutek Wilk: "Re: [Xen-devel] [PATCH 4/4] xen/events: Add WARN_ON when quicklookup found invalid type."
Previous message: Indan Zupancic: "Re: [RFC PATCH 0/3] move the secure_computing call"
In reply to: Stefano Stabellini: "Re: [PATCH 3/4] xen/hvc: Check HVM_PARAM_CONSOLE_[EVTCHN|PFN] forcorrectness."
Next in thread: Stefano Stabellini: "Re: [Xen-devel] [PATCH 3/4] xen/hvc: Check HVM_PARAM_CONSOLE_[EVTCHN|PFN]for correctness."
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

> I think that we should add a comment stating that even though mfn = 0
> and evtchn = 0 are theoretically correct values, in practice they never
> are and they mean that a legacy toolstack hasn't initialized the pv
> console correctly.

Like this?

Next message: Konrad Rzeszutek Wilk: "Re: [Xen-devel] [PATCH 4/4] xen/events: Add WARN_ON when quicklookup found invalid type."
Previous message: Indan Zupancic: "Re: [RFC PATCH 0/3] move the secure_computing call"
In reply to: Stefano Stabellini: "Re: [PATCH 3/4] xen/hvc: Check HVM_PARAM_CONSOLE_[EVTCHN|PFN] forcorrectness."
Next in thread: Stefano Stabellini: "Re: [Xen-devel] [PATCH 3/4] xen/hvc: Check HVM_PARAM_CONSOLE_[EVTCHN|PFN]for correctness."
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]