public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sheng Yang <sheng@linux.intel.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Keir Fraser <keir.fraser@eu.citrix.com>,
	Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>,
	"xen-devel" <xen-devel@lists.xensource.com>,
	Eddie Dong <eddie.dong@intel.com>,
	linux-kernel@vger.kernel.org,
	Jun Nakajima <jun.nakajima@intel.com>
Subject: Re: [Xen-devel] [RFC][PATCH 07/10] xen/hybrid: Add PV timer support
Date: Thu, 17 Sep 2009 13:54:51 +0800	[thread overview]
Message-ID: <200909171354.52543.sheng@linux.intel.com> (raw)
In-Reply-To: <4AB149BA.1000106@goop.org>

On Thursday 17 September 2009 04:25:30 Jeremy Fitzhardinge wrote:
> On 09/16/09 01:42, Sheng Yang wrote:
> > If we have event channel, we can use VIRQ_TIMER to deliver timer
> > interrupt, otherwise we would reuse IRQ0.
>
> What's the purpose of this?  Why can we get a timer virq via event
> channel as usual?  I'm very dubious about having any platform
> interrupts/apic interaction in this code.
>
>     J

Before this patch, we didn't enable event channel for hybrid guest. But I 
think it's reasonable to enable it. Separating the event channel patch into 
two, one for generic usage, and another one QEmu devices. I would try to do 
this.

-- 
regards
Yang, Sheng

  reply	other threads:[~2009-09-17  5:54 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-16  8:42 [RFC][PATCH 0/10] Xen Hybrid extension support Sheng Yang
2009-09-16  8:42 ` [RFC][PATCH 01/10] xen/pvhvm: add support for hvm_op Sheng Yang
2009-09-16  8:42 ` [RFC][PATCH 02/10] xen/hybrid: Import cpuid.h from Xen Sheng Yang
2009-09-16  8:42 ` [RFC][PATCH 03/10] xen/hybrid: Xen Hybrid Extension initialization Sheng Yang
2009-09-16 20:24   ` [Xen-devel] " Jeremy Fitzhardinge
2009-09-17  6:22     ` Keir Fraser
2009-09-17 16:46       ` Jeremy Fitzhardinge
2009-09-16  8:42 ` [RFC][PATCH 04/10] xen/hybrid: Modify pv_init_ops and xen_info Sheng Yang
2009-09-16  8:42 ` [RFC][PATCH 05/10] xen/hybrid: Add PV halt support Sheng Yang
2009-09-16  8:42 ` [RFC][PATCH 06/10] xen/hybrid: Add shared_info page for xen Sheng Yang
2009-09-16  8:42 ` [RFC][PATCH 07/10] xen/hybrid: Add PV timer support Sheng Yang
2009-09-16 20:25   ` [Xen-devel] " Jeremy Fitzhardinge
2009-09-17  5:54     ` Sheng Yang [this message]
2009-09-16  8:42 ` [RFC][PATCH 08/10] x86: Don't ack_APIC_irq() if lapic is disabled in GENERIC_INTERRUPT_VECTOR handler Sheng Yang
2009-09-16  8:58   ` Cyrill Gorcunov
2009-09-16  9:03     ` Cyrill Gorcunov
2009-09-16  9:37       ` Cyrill Gorcunov
2009-09-17  3:54         ` Sheng Yang
2009-09-16  8:42 ` [RFC][PATCH 09/10] xen/hybrid: Make event channel work with QEmu emulated devices Sheng Yang
2009-09-16 20:35   ` [Xen-devel] " Jeremy Fitzhardinge
2009-09-17  5:58     ` Sheng Yang
2009-09-16  8:42 ` [RFC][PATCH 10/10] xen/hybrid: Enable grant table and xenbus Sheng Yang
2009-09-16 13:31 ` [Xen-devel] [RFC][PATCH 0/10] Xen Hybrid extension support Konrad Rzeszutek Wilk
2009-09-17  8:59   ` Sheng Yang

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=200909171354.52543.sheng@linux.intel.com \
    --to=sheng@linux.intel.com \
    --cc=eddie.dong@intel.com \
    --cc=jeremy.fitzhardinge@citrix.com \
    --cc=jeremy@goop.org \
    --cc=jun.nakajima@intel.com \
    --cc=keir.fraser@eu.citrix.com \
    --cc=linux-kernel@vger.kernel.org \
    --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