From: Keir Fraser <keir.xen@gmail.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] x86: rework hypercall argument translation area setup
Date: Thu, 21 Feb 2013 12:57:17 +0000 [thread overview]
Message-ID: <CD4BCA2D.4C5CD%keir.xen@gmail.com> (raw)
In-Reply-To: <5126206902000078000BFE26@nat28.tlf.novell.com>
On 21/02/2013 12:26, "Jan Beulich" <JBeulich@suse.com> wrote:
>> Well, fine in principle. This manual setup/teardown of l2/l1 pagetables in
>> the perdomain area is getting a bit tiresome though isn't it? Isn't there
>> some setup helper that could be abstracted out for all users, and perhaps
>> even some automated teardown-and-freeing on domain destroy? I just sighed
>> when I saw more skanky pagetable manipulation for what is a conceptually
>> simple change.
>
> I tried to spot pieces worth folding into helper functions, but
> didn't really find anything worthwhile (the purposes of the
> mappings are just too different). Perhaps we could have a
> map_pages_to_guest(), taking care of all intermediate page
> table levels? I can't see much else, and the main problem is that
> of tracking pages used for page tables here anyway.
Well, possibly even that might be an improvement.
> Are we concerned about the performance of guest GDT/LDT page
> (un)mappings?
LDT must often change on guest process context switch? So I would think yes
we do.
-- Keir
next prev parent reply other threads:[~2013-02-21 12:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-21 11:42 [PATCH] x86: rework hypercall argument translation area setup Jan Beulich
2013-02-21 12:08 ` Keir Fraser
2013-02-21 12:26 ` Jan Beulich
2013-02-21 12:57 ` Keir Fraser [this message]
2013-02-21 13:05 ` Jan Beulich
2013-02-21 13:12 ` 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=CD4BCA2D.4C5CD%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=JBeulich@suse.com \
--cc=xen-devel@lists.xen.org \
/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.