xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@novell.com>
To: Keir Fraser <keir.xen@gmail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [xen-unstable test] 6947: regressions - trouble: broken/fail/pass
Date: Mon, 02 May 2011 13:24:59 +0100	[thread overview]
Message-ID: <4DBEBEBB020000780003F295@vpn.id2.novell.com> (raw)
In-Reply-To: <C9E45E5C.17154%keir.xen@gmail.com>

>>> On 02.05.11 at 14:13, Keir Fraser <keir.xen@gmail.com> wrote:
> On 02/05/2011 13:00, "Jan Beulich" <JBeulich@novell.com> wrote:
> 
>>> (2) Change the xmalloc lock to spin_lock_irqsave(). This would also have to
>>> be transitively applied to at least the heap_lock in page_alloc.c. One issue
>>> with this (and indeed with calling alloc_heap_pages at all with IRQs
>>> disabled) is that alloc_heap_pages does actually assume IRQs are enabled
>>> (for example, it calls flush_tlb_mask()) -- actually I think this limitation
>>> probably predates the tsc rendezvous changes, and could be a source of
>>> latent bugs in earlier Xen releases.
>> 
>> (2b) Make only the xmalloc() lock disable IRQs, and don't allow it to
>> go into the page allocator when IRQs were disabled on entry. Have
>> a reserve page available on each pCPU (requires that in a single
>> hypercall there can't be allocations adding up to more than PAGE_SIZE),
>> and when consumed, re-fill this page e.g. from a softirq or tasklet.
> 
> You'd have to release/acquire the xmalloc lock across the ->get_mem call.

Not sure what you're trying to make me aware of - initial acquire
would be spin_lock_irqsave(), prior to ->get_mem() it would
spin_unlock_irqrestore(), and the ->get_mem() handler would be
responsible for not calling into the page allocator when interrupts
are (still) disabled (and instead use the per-CPU reserve page if
populated, triggering its re-population).

Jan

  reply	other threads:[~2011-05-02 12:24 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-01 19:56 [xen-unstable test] 6947: regressions - trouble: broken/fail/pass xen.org
2011-05-01 20:48 ` Keir Fraser
2011-05-02  9:01   ` Jan Beulich
2011-05-02 11:22     ` Keir Fraser
2011-05-02 12:00       ` Jan Beulich
2011-05-02 12:13         ` Keir Fraser
2011-05-02 12:24           ` Jan Beulich [this message]
2011-05-02 12:19         ` Keir Fraser
2011-05-02 12:29           ` Jan Beulich
2011-05-02 13:14             ` Keir Fraser
2011-05-02 13:39               ` Keir Fraser
2011-05-02 14:04               ` Jan Beulich
2011-05-02 15:45                 ` Keir Fraser
2011-05-02 16:36                   ` Dan Magenheimer
2011-05-02 17:07                     ` Keir Fraser
2011-05-03  9:35           ` Jan Beulich
2011-05-03 10:09             ` Keir Fraser
2011-05-03 13:36               ` Jan Beulich
2011-05-03 14:09                 ` 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=4DBEBEBB020000780003F295@vpn.id2.novell.com \
    --to=jbeulich@novell.com \
    --cc=keir.xen@gmail.com \
    --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).