From: Keir Fraser <keir.xen@gmail.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH 0/2] make hypercall preemption checks consistent
Date: Thu, 13 Mar 2014 10:26:13 +0000 [thread overview]
Message-ID: <532187C5.9050002@gmail.com> (raw)
In-Reply-To: <5315C5370200007800120CE4@nat28.tlf.novell.com>
[-- Attachment #1.1: Type: text/plain, Size: 420 bytes --]
> Jan Beulich <mailto:JBeulich@suse.com>
> 4 March 2014 11:21
> - never preempt on the first iteration (ensure forward progress)
> - never preempt on the last iteration (pointless/wasteful)
> - do cheap checks first
>
> 1: common: make hypercall preemption checks consistent
> 2: x86: make hypercall preemption checks consistent
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
>
Acked-by: Keir Fraser <keir@xen.org>
[-- Attachment #1.2.1: Type: text/html, Size: 1789 bytes --]
[-- Attachment #1.2.2: compose-unknown-contact.jpg --]
[-- Type: image/jpeg, Size: 770 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2014-03-13 10:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-04 11:21 [PATCH 0/2] make hypercall preemption checks consistent Jan Beulich
2014-03-04 11:24 ` [PATCH 1/2] common: " Jan Beulich
2014-03-04 11:29 ` Andrew Cooper
2014-03-04 11:26 ` [PATCH 2/2] x86: " Jan Beulich
2014-03-04 11:35 ` Andrew Cooper
2014-03-04 11:30 ` [PATCH 0/2] " Jan Beulich
2014-03-11 11:38 ` Ian Campbell
2014-03-04 11:46 ` Tim Deegan
2014-03-04 11:52 ` Andrew Cooper
2014-03-04 12:00 ` Jan Beulich
2014-03-04 12:10 ` David Vrabel
2014-03-04 13:06 ` Jan Beulich
2014-03-04 14:07 ` David Vrabel
2014-03-12 9:35 ` Ping: " Jan Beulich
2014-03-13 10:26 ` Keir Fraser [this message]
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=532187C5.9050002@gmail.com \
--to=keir.xen@gmail.com \
--cc=JBeulich@suse.com \
--cc=xen-devel@lists.xenproject.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 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).