All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sheng Yang <sheng@linux.intel.com>
To: Amit Shah <amit.shah@redhat.com>
Cc: avi@redhat.com, kvm@vger.kernel.org,
	xiantao zhang <xiantao.zhang@intel.com>
Subject: Re: [PATCH 1/2] KVM: Handle multiple interrupt sources
Date: Mon, 13 Oct 2008 13:10:55 +0800	[thread overview]
Message-ID: <200810131310.56577.sheng@linux.intel.com> (raw)
In-Reply-To: <81778567.14531223874378653.JavaMail.root@zmail02.collab.prod.int.phx2.redhat.com>

On Monday 13 October 2008 13:06:18 Amit Shah wrote:
> ----- "Sheng Yang" <sheng@linux.intel.com> wrote:
> > On Saturday 11 October 2008 16:10:51 Amit Shah wrote:
> > > From: Sheng Yang <sheng@linux.intel.com>
> > >
> > > Keep a record of current interrupt state before injecting. Don't
> > > assert/deassert repeatedly, so that every caller of kvm_set_irq()
> > > can be identified as a separate interrupt source for the IOAPIC/PIC
> > > to implement logical OR of level triggered interrupts on one IRQ
> >
> > line.
> >
> > > Notice that userspace devices are treated as one device for each
> >
> > IRQ
> >
> > > line. The correctness of sharing interrupt for each IRQ line should
> >
> > be
> >
> > > ensured by the userspace program (QEmu).
> > >
> > > [Amit: rebase to kvm.git HEAD]
> >
> > Hi, Amit
> >
> > Thanks for your work!
> >
> > But maybe I miss something. I suppose my later patch can work
> > indepently? I
> > think the second patch should solve the whole problem (sorry to reply
> > it to
> > the second rather than [0/2] which made confusion...). Can you have a
> > check?
>
> I'm not sure I understand. Which concern are you talking about?
>
> I used the latest patch that you sent and I also verified that it works.
>
Well, at least I meant to replace all of my first two patches with my later 
one... I suppose the second patch(my later one, derived from Avi's 
suggestion) should work alone without the first one...
--
regards
Yang, Sheng

  reply	other threads:[~2008-10-13  5:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <90486638.14481223874204346.JavaMail.root@zmail02.collab.prod.int.phx2.redhat.com>
2008-10-13  5:06 ` [PATCH 1/2] KVM: Handle multiple interrupt sources Amit Shah
2008-10-13  5:10   ` Sheng Yang [this message]
2008-10-13  6:39     ` Amit Shah
2008-10-11  8:10 Support sharing of guest IRQ levels for assigned devices Amit Shah
2008-10-11  8:10 ` [PATCH 1/2] KVM: Handle multiple interrupt sources Amit Shah
2008-10-13  2:32   ` 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=200810131310.56577.sheng@linux.intel.com \
    --to=sheng@linux.intel.com \
    --cc=amit.shah@redhat.com \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=xiantao.zhang@intel.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.