From: Keir Fraser <keir.xen@gmail.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
Xen-devel <xen-devel@lists.xen.org>
Cc: Tim Deegan <tim@xen.org>, Jan Beulich <JBeulich@suse.com>
Subject: Re: [PATCH v2] x86/mm: Ensure useful progress in alloc_l2_table()
Date: Wed, 03 Jul 2013 13:41:02 +0100 [thread overview]
Message-ID: <CDF9DA6E.2BF6C%keir.xen@gmail.com> (raw)
In-Reply-To: <1372854537-4897-1-git-send-email-andrew.cooper3@citrix.com>
On 03/07/2013 13:28, "Andrew Cooper" <andrew.cooper3@citrix.com> wrote:
> While debugging the issue which turned out to be XSA-58, a printk in this loop
> showed that it was quite easy to never make useful progress, because of
> consistently failing the preemption check.
>
> One single l2 entry is a reasonable amount of work to do, even if an action is
> pending, and also assures forwards progress across repeat continuations.
>
> Tweak the continuation criteria to fail on the first iteration of the loop.
>
> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
> Cc: Keir <keir@xen.org>
Acked-by: Keir Fraser <keir@xen.org>
> Cc: Jan Beulich <JBeulich@suse.com>
> Cc: Tim Deegan <tim@xen.org>
>
> ---
> Changes since v1:
> * Dont move the continuation block to the end
> ---
> xen/arch/x86/mm.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/xen/arch/x86/mm.c b/xen/arch/x86/mm.c
> index 77dcafc..f151dec 100644
> --- a/xen/arch/x86/mm.c
> +++ b/xen/arch/x86/mm.c
> @@ -1278,7 +1278,8 @@ static int alloc_l2_table(struct page_info *page,
> unsigned long type,
>
> for ( i = page->nr_validated_ptes; i < L2_PAGETABLE_ENTRIES; i++ )
> {
> - if ( preemptible && i && hypercall_preempt_check() )
> + if ( preemptible && i > page->nr_validated_ptes
> + && hypercall_preempt_check() )
> {
> page->nr_validated_ptes = i;
> rc = -EAGAIN;
prev parent reply other threads:[~2013-07-03 12:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-03 12:28 [PATCH v2] x86/mm: Ensure useful progress in alloc_l2_table() Andrew Cooper
2013-07-03 12:41 ` 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=CDF9DA6E.2BF6C%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=tim@xen.org \
--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 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).