From: Keir Fraser <keir@xensource.com>
To: "Xu, Anthony" <anthony.xu@intel.com>
Cc: xen-devel@lists.xensource.com,
xen-ia64-devel <xen-ia64-devel@lists.xensource.com>
Subject: Re: [RFC]degradation on IPF due to hypercall set irq
Date: Wed, 22 Nov 2006 09:26:20 +0000 [thread overview]
Message-ID: <C189C83C.4DCA%keir@xensource.com> (raw)
In-Reply-To: <51CFAB8CB6883745AE7B93B3E084EBE207DD53@pdsmsx412.ccr.corp.intel.com>
On 22/11/06 09:24, "Xu, Anthony" <anthony.xu@intel.com> wrote:
>>>> To clarify, by event/main loop I mean: Flush just before qemu blocks
>>>> (otherwise multicall can be held for unbounded time, unless we set a
>>>> batching timeout which hopefully we can avoid needing to do).
>
> Why otherwise multicall can be held for unbounded time?
Qemu only wakes up for device-model accesses. We don't know when the next of
those will be. So we should flush multicalls before the potentially blocking
select().
-- Keir
next prev parent reply other threads:[~2006-11-22 9:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-22 9:24 [RFC]degradation on IPF due to hypercall set irq Xu, Anthony
2006-11-22 9:26 ` Keir Fraser [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-11-24 15:53 Xu, Anthony
2006-11-24 14:45 [Xen-devel][RFC]degradation " Xu, Anthony
2006-11-24 15:28 ` [RFC]degradation " Keir Fraser
2006-11-24 7:08 Xu, Anthony
2006-11-24 9:46 ` Keir Fraser
2006-11-23 1:51 Xu, Anthony
2006-11-22 10:23 [Xen-devel][RFC]degradation " Xu, Anthony
2006-11-22 10:27 ` [RFC]degradation " Keir Fraser
2006-11-22 9:38 [Xen-devel][RFC]degradation " Xu, Anthony
2006-11-22 9:47 ` [RFC]degradation " Keir Fraser
2006-11-22 8:16 Xu, Anthony
2006-11-22 9:21 ` Keir Fraser
2006-11-22 7:55 [Xen-devel][RFC]degradation " Keir Fraser
2006-11-22 7:58 ` [RFC]degradation " Keir Fraser
2006-11-22 7:43 Xu, Anthony
2006-11-22 3:33 Xu, Anthony
2006-11-22 7:06 ` 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=C189C83C.4DCA%keir@xensource.com \
--to=keir@xensource.com \
--cc=anthony.xu@intel.com \
--cc=xen-devel@lists.xensource.com \
--cc=xen-ia64-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 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.