From: "Jan Beulich" <JBeulich@novell.com>
To: Keir Fraser <keir@xen.org>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] Enble 6 argument hypercalls for HVMs
Date: Wed, 15 Dec 2010 12:12:01 +0000 [thread overview]
Message-ID: <4D08BEA102000078000281FE@vpn.id2.novell.com> (raw)
In-Reply-To: <C92E5A71.2907C%keir@xen.org>
>>> On 15.12.10 at 12:43, Keir Fraser <keir@xen.org> wrote:
> On 15/12/2010 10:40, "Jan Beulich" <JBeulich@novell.com> wrote:
>> Looking at this code also makes me wonder once again whether
>> it really is a good idea to have a generally not taken forward
>> branch here.
>
> Which generally not-taken branch? The 'je 1f' instruction generally *will*
> be taken!
Oops, of course - it being taken is the problem, as it'll be statically
mis-predicted.
Jan
next prev parent reply other threads:[~2010-12-15 12:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-14 22:16 [PATCH] Enble 6 argument hypercalls for HVMs Ross Philipson
2010-12-15 9:07 ` Jan Beulich
2010-12-15 10:06 ` Keir Fraser
2010-12-15 10:40 ` Jan Beulich
2010-12-15 11:43 ` Keir Fraser
2010-12-15 12:12 ` Jan Beulich [this message]
2010-12-15 13:20 ` 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=4D08BEA102000078000281FE@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=keir@xen.org \
--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 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).