From: Gerd Hoffmann <kraxel@suse.de>
To: Keir Fraser <keir@xensource.com>
Cc: Xen devel list <xen-devel@lists.xensource.com>
Subject: Re: Re: changeset 13403 ...
Date: Mon, 29 Jan 2007 15:47:41 +0100 [thread overview]
Message-ID: <45BE090D.1050209@suse.de> (raw)
In-Reply-To: <C1E3AD3A.8609%keir@xensource.com>
Keir Fraser wrote:
>
>
> On 29/1/07 13:48, "Keir Fraser" <keir@xensource.com> wrote:
>
>> On 29/1/07 13:40, "Gerd Hoffmann" <kraxel@suse.de> wrote:
>>
>>> Just noticed that domU kexec doesn't work any more, changeset 13403 is
>>> the culpit. Hmm. No, it isn't easy to work-around ...
>>>
>>> cheers,
>> Two pagetable switches in a single multicall? First switch is to a pagetable
>> which maps only the multicall structure. This small intermediate table has
>> to be mapped read-only in the original pagetables and in the final
>> pagetables, but it will only be a few pages of memory (4 in the worst case).
Helps a bit, but doesn't solve the fundamental problem that I can't use
the page tables created by the domain-builder as-is.
> Oh, it'll need a hypercall transfer page too. And it's a mmuext_op list that
> you need, not a multicall. The transfer page and mmuext_op list can be
> placed in adjacent pages so that you don't need any more intermediate
> pagetable pages.
Hmm. hypercall transfer page? The one with the int 82h instructions?
Is the mmuext_op list copyed over before running it? If so, the it
should not be required to be mapped all the time, right? In that case I
could get away with an empty page as page directory? Or maybe even
baseptr=NULL?
cheers,
Gerd
--
Gerd Hoffmann <kraxel@suse.de>
next prev parent reply other threads:[~2007-01-29 14:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-29 13:40 changeset 13403 Gerd Hoffmann
2007-01-29 13:48 ` Keir Fraser
2007-01-29 13:55 ` Keir Fraser
2007-01-29 14:47 ` Gerd Hoffmann [this message]
2007-01-29 15:06 ` Keir Fraser
2007-01-29 15:35 ` Gerd Hoffmann
[not found] <E1HBaxo-0007rv-SQ@host-192-168-0-1-bcn-london>
2007-01-29 18:36 ` Joe Bonasera
2007-01-29 18:38 ` Keir Fraser
2007-02-01 16:10 ` Gerd Hoffmann
2007-02-01 18:30 ` Keir Fraser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45BE090D.1050209@suse.de \
--to=kraxel@suse.de \
--cc=keir@xensource.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.