From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Jinsong Liu <jinsong.liu@intel.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Keir Fraser <keir@xen.org>,
"suravee.suthikulpanit@amd.com" <suravee.suthikulpanit@amd.com>,
"zhenzhong.duan@oracle.com" <zhenzhong.duan@oracle.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Will Auld <will.auld@intel.com>,
Jun Nakajima <jun.nakajima@intel.com>,
"sherry.hurwitz@amd.com" <sherry.hurwitz@amd.com>
Subject: Re: XSA-60 solutions
Date: Mon, 7 Oct 2013 16:08:25 +0100 [thread overview]
Message-ID: <5252CE69.90005@citrix.com> (raw)
In-Reply-To: <5252E9B002000078000F94E6@nat28.tlf.novell.com>
On 07/10/13 16:04, Jan Beulich wrote:
>>>> On 07.10.13 at 16:29, "Liu, Jinsong" <jinsong.liu@intel.com> wrote:
>> Any comments/suggestions?
> As pointed out in earlier private conversation, I think that the dual
> table approach would be preferable if it can be made work.
>
> I'm surprised no-one from Oracle responded so far, as it was them
> originally having found the issue.
>
> Jan
>
>
I cant remember whether I asked this before or not, but is there a
reason why this cant be done in the same way as hypercall continuations?
~Andrew
next prev parent reply other threads:[~2013-10-07 15:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-30 20:42 XSA-60 solutions Liu, Jinsong
2013-10-07 14:29 ` Liu, Jinsong
2013-10-07 15:04 ` Jan Beulich
2013-10-07 15:08 ` Andrew Cooper [this message]
2013-10-07 15:23 ` Jan Beulich
2013-10-07 16:03 ` Liu, Jinsong
2013-10-08 7:40 ` Jan Beulich
2013-10-09 10:41 ` Liu, Jinsong
2013-10-09 11:40 ` Jan Beulich
2013-10-09 18:01 ` Tim Deegan
2013-10-08 2:25 ` DuanZhenzhong
2013-10-08 7:37 ` Jan Beulich
-- strict thread matches above, loose matches on Subject: below --
2013-09-30 20:28 Liu, Jinsong
2013-10-01 13:44 ` Konrad Rzeszutek Wilk
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=5252CE69.90005@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=jinsong.liu@intel.com \
--cc=jun.nakajima@intel.com \
--cc=keir@xen.org \
--cc=sherry.hurwitz@amd.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=will.auld@intel.com \
--cc=xen-devel@lists.xen.org \
--cc=xen-devel@lists.xensource.com \
--cc=zhenzhong.duan@oracle.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.