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

Re: [Xen-devel] [RFC][PATCH 4/5] tools:firmware:hvmloader: reserve RMRR mappings in e820

> From: Jan Beulich [mailto:JBeulich@xxxxxxxx]
> Sent: Sunday, August 10, 2014 11:53 PM
> >>> On 08.08.14 at 23:47, <kevin.tian@xxxxxxxxx> wrote:
> >>  From: Chen, Tiejun
> >> Sent: Thursday, August 07, 2014 4:03 AM
> >>
> >> We need to reserve all RMRR mappings in e820 to avoid any
> >> potential guest memory conflict.
> >
> > strictly speaking besides reserving in e820, you should also poke later
> > MMIO BAR allocations to avoid confliction too. Currently it's relative
> > to low_mem_pgend, which is likely to be different from host layout
> > so it's still possible to see a virtual MMIO bar base conflicting to the
> > RMRR ranges which are supposed to be sparse.
> Correct. And what's worse: Possible collisions between RMRRs and
> the BIOS we place into the VM need to be taken care of, which may
> turn out rather tricky.

right that becomes tricky. We can provide another hypercall to allow a 
VM tell Xen which RMRR can't be assigned due to confliction with gust
BIOS or other hvmloader allocation (if confliction can't be resolved).

If Xen detects a device owning RMRR is already assigned to the VM,
then fail the hypercall and hvmloader just panic with information to
indicate confliction.

Otherwise Xen records the information and future dynamic device
assignment like hotplug will be failed if associated RMRR will be in
the confliction list.


Xen-devel mailing list



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