[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH, v2] add privileged/unprivileged kernel feature indication

>>> On 21.07.11 at 10:50, Keir Fraser <keir@xxxxxxx> wrote:
> On 21/07/2011 09:16, "Jan Beulich" <JBeulich@xxxxxxxxxx> wrote:
>>> You say it is a Linux notion that dom0 implies domU but I am not aware
>>> of any PV OS which supports dom0 that doesn't also support domU, do you
>>> have specific examples of OSes which are dom0-only?
>> No, I'm not aware of any existing ones, but I also wasn't in favor of
>> the move to imply unprivileged capabilities when Linux is configured
>> as privileged guest (iirc this wasn't the case from the very beginning).
>> And again, imo an interface like the hypervisor's shouldn't dictate any
>> kind of policy on the guest OSes.
> My own issue with the unprivileged flag is that I'm not clear what it
> actually means. When would you *not* set it? I mean it looks in the Linux
> side you set it unconditionally right now. What's the point? Why not remove
> the flag and introduce it when we have good reason and can attach meaningful
> semantics to it?

Again - you're talking about an actual guest side implementation (which,
in this particular case, has to honor how the rest of the implementation
is done, i.e. it has to set the flag unconditionally). I'm talking about an
abstract interface definition that should suit everyone (existing as well
as yet to come).

> There we are, we're two against one now ;-)

Still hoping you both get my point. If not, I'll have to give in without
being convinced.


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.