* backend config options
@ 2006-03-07 10:17 Jan Beulich
2006-03-07 10:29 ` Keir Fraser
0 siblings, 1 reply; 2+ messages in thread
From: Jan Beulich @ 2006-03-07 10:17 UTC (permalink / raw)
To: xen-devel
Shouldn't all the backend config options only be available in privileged kernels? If not, what usage scenario would
there be for a backend enabled in a domU?
Thanks, Jan
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: backend config options
2006-03-07 10:17 backend config options Jan Beulich
@ 2006-03-07 10:29 ` Keir Fraser
0 siblings, 0 replies; 2+ messages in thread
From: Keir Fraser @ 2006-03-07 10:29 UTC (permalink / raw)
To: Jan Beulich; +Cc: xen-devel
On 7 Mar 2006, at 10:17, Jan Beulich wrote:
> Shouldn't all the backend config options only be available in
> privileged kernels? If not, what usage scenario would
> there be for a backend enabled in a domU?
PRIVILEGED_GUEST is only intended to enable domain0 functionality --
mostly it enables building our modified BIOS-table parsing and IO-APIC
files. You can still build a domU with a PCI stack and real device
drivers and grant that domU limited access to hardware resources. In
that case it would be very reasonable to build it with a backend driver
too, so it can multiplex its hardware resources.
-- Keir
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2006-03-07 10:29 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-03-07 10:17 backend config options Jan Beulich
2006-03-07 10:29 ` Keir Fraser
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.