From: "Jan Beulich" <JBeulich@novell.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>,
Yunhong Jiang <yunhong.jiang@intel.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: [RFC] [PATCH] Dom0: Don't switch back to user space stack in syscall entry
Date: Thu, 11 Feb 2010 08:53:43 +0000 [thread overview]
Message-ID: <4B73D3A7020000780002EE6D@vpn.id2.novell.com> (raw)
In-Reply-To: <4B72F72F.3080107@goop.org>
>>> Jeremy Fitzhardinge <jeremy@goop.org> 10.02.10 19:13 >>>
>> b) Add IST support to xen hypervisor, Considering the ptrace issue in http://lists.xensource.com/archives/html/xen-devel/2009-05/msg00200.html and also Ingo's comments in http://lkml.indiana.edu/hypermail/linux/kernel/0905.1/00087.html, maybe it still have value to add such support. But not sure if that is accepetable for xen hypervisor.
>>
>
>That would depend on Keir's thoughts, which I would guess depend on what
>the patch and ABI would look like. It's certainly the most general
>solution if it can be done in a reasonable way.
But if at all, I'd recommend considering a properly nesting solution
rather than just to mimic hardware behavior (since there's no IDT,
functionality needs to differ from native anyway).
Jan
next prev parent reply other threads:[~2010-02-11 8:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-28 10:26 [RFC] [PATCH] Dom0: Don't switch back to user space stack in syscall entry Jiang, Yunhong
2010-02-10 18:13 ` Jeremy Fitzhardinge
2010-02-11 7:42 ` Jiang, Yunhong
2010-02-11 8:55 ` Jan Beulich
2010-02-11 8:53 ` Jan Beulich [this message]
2010-02-12 4:30 ` Jiang, Yunhong
2010-02-12 8:16 ` Jan Beulich
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=4B73D3A7020000780002EE6D@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=jeremy@goop.org \
--cc=keir.fraser@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
--cc=yunhong.jiang@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).