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

Re: [Xen-devel] [PATCH] ACPI/APEI: fix ERST MOVE_DATA instruction implementation

  • To: Jan Beulich <JBeulich@xxxxxxxx>
  • From: Keir Fraser <keir@xxxxxxx>
  • Date: Wed, 17 Oct 2012 14:01:54 +0100
  • Cc: xen-devel <xen-devel@xxxxxxxxxxxxx>
  • Delivery-date: Wed, 17 Oct 2012 13:02:29 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xen.org>
  • Thread-index: Ac2sZ5SzaLg0ByL5zUqjMLrWQiMpcA==
  • Thread-topic: [Xen-devel] [PATCH] ACPI/APEI: fix ERST MOVE_DATA instruction implementation

On 17/10/2012 13:15, "Jan Beulich" <JBeulich@xxxxxxxx> wrote:

>>>> On 17.10.12 at 14:07, Keir Fraser <keir@xxxxxxx> wrote:
>> On 17/10/2012 12:53, "Jan Beulich" <JBeulich@xxxxxxxx> wrote:
>>> Before anyone asks - yes, I have added to my todo list to put in
>>> place a proper ioremap() for x86. But since I'm under some time
>>> pressure right now, this was the faster route to something that
>>> can be committed to see whether the regression goes away.
>> That's good as we'll need it for >4kB per-VCPU stacks (even if we only need
>> 4kB VCPU stacks, we'll want a guard page too).
> But why would you want to do that via ioremap()?

Well the required missing mechanism is the same, right? The ability to
allocate some unused virtual address space. We already have
map_pages_to_xen(), so it's just the allocation part that is missing for
either ioremap() or vcpu stacks.

 -- Keir

> Jan

Xen-devel mailing list



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