From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Keir <keir@xen.org>, Xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] x86/mm: Ensure useful progress in alloc_l2_table()
Date: Wed, 3 Jul 2013 13:20:37 +0100 [thread overview]
Message-ID: <51D41715.2040402@citrix.com> (raw)
In-Reply-To: <51D4325302000078000E27C6@nat28.tlf.novell.com>
On 03/07/13 13:16, Jan Beulich wrote:
>>>> On 03.07.13 at 13:37, Andrew Cooper <andrew.cooper3@citrix.com> wrote:
>> --- a/xen/arch/x86/mm.c
>> +++ b/xen/arch/x86/mm.c
>> @@ -1278,13 +1278,6 @@ 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() )
>> - {
>> - page->nr_validated_ptes = i;
>> - rc = -EAGAIN;
>> - break;
>> - }
>> -
>> if ( !is_guest_l2_slot(d, type, i) ||
>> (rc = get_page_from_l2e(pl2e[i], pfn, d)) > 0 )
>> continue;
>> @@ -1299,6 +1292,14 @@ static int alloc_l2_table(struct page_info *page, unsigned long type,
>> }
>>
>> adjust_guest_l2e(pl2e[i], d);
>> +
>> + if ( preemptible && i != L2_PAGETABLE_ENTRIES
> if ( preemptible && i != L2_PAGETABLE_ENTRIES - 1
>
> But an even smaller change would be to change the if() you remove
> above to
>
> if ( preemptible && i > page->nr_validated_ptes &&
> hypercall_preempt_check() )
>
> Jan
So it will - I shall resend v2
~Andrew
>
>> + && hypercall_preempt_check() )
>> + {
>> + page->nr_validated_ptes = i + 1;
>> + rc = -EAGAIN;
>> + break;
>> + }
>> }
>>
>> if ( rc >= 0 && (type & PGT_pae_xen_l2) )
>
prev parent reply other threads:[~2013-07-03 12:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-03 11:37 [PATCH] x86/mm: Ensure useful progress in alloc_l2_table() Andrew Cooper
2013-07-03 12:16 ` Jan Beulich
2013-07-03 12:20 ` Andrew Cooper [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=51D41715.2040402@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=keir@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 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.