From: Keir Fraser <keir@xensource.com>
To: "Xu, Anthony" <anthony.xu@intel.com>, Keir Fraser <keir@xensource.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: Fri, 24 Nov 2006 09:46:47 +0000 [thread overview]
Message-ID: <C18C7007.4F8F%keir@xensource.com> (raw)
In-Reply-To: <51CFAB8CB6883745AE7B93B3E084EBE207DD59@pdsmsx412.ccr.corp.intel.com>
On 24/11/06 07:08, "Xu, Anthony" <anthony.xu@intel.com> wrote:
> This patch is for comments, and it is based on IPF, it may not apply to IA32
> side.
>
> This patch delivers interrupt and IO finish in the same hypercall
> xc_hvm_set_irq_and_wakeup_cpu,
> This eliminate all unnecessary hypercalls.
> In the meantime, I add a mechanism for IDE DMA thread to wakeup qemu main
> block(select) to
> Deliver IDE DMA interrupt.
Firstly, this patch is not against unstable tip.
Secondly, we should make multicalls work rather than kludge a
set_irq_and_notify_io_done type of hypercall. Applications are free to
include any of the Xen public headers. We really just need a xc_multicall()
API function.
Thirdly, either we should keep the independent IDE-DMA thread or it should
be entirely incorporated into the main qemu thread. Are pipe writes much
faster than just doing a hypercall? If much slower, why is that? Could you
work out a way of generically making IPC hypercalls faster (particularly
from privileged user space -- could you trap straight to the hypervisor from
user space rather than bouncing through guest kernel?).
-- Keir
next prev parent reply other threads:[~2006-11-24 9:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-24 7:08 [RFC]degradation on IPF due to hypercall set irq Xu, Anthony
2006-11-24 9:46 ` 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-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 9:24 Xu, Anthony
2006-11-22 9:26 ` 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=C18C7007.4F8F%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.