Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: Marc Zyngier <marc.zyngier@arm.com>
To: Christoffer Dall <christoffer.dall@linaro.org>,
	Eric Auger <eric.auger@linaro.org>
Cc: "eric.auger@st.com" <eric.auger@st.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"alex.williamson@redhat.com" <alex.williamson@redhat.com>,
	"joel.schopp@amd.com" <joel.schopp@amd.com>,
	"kim.phillips@freescale.com" <kim.phillips@freescale.com>,
	"paulus@samba.org" <paulus@samba.org>,
	"gleb@kernel.org" <gleb@kernel.org>,
	"pbonzini@redhat.com" <pbonzini@redhat.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"patches@linaro.org" <patches@linaro.org>,
	Will Deacon <Will.Deacon@arm.com>,
	"a.motakis@virtualopensystems.com"
	<a.motakis@virtualopensystems.com>,
	"a.rigo@virtualopensystems.com" <a.rigo@virtualopensystems.com>,
	"john.liuli@huawei.com" <john.liuli@huawei.com>,
	"ming.lei@canonical.com" <ming.lei@canon
Subject: Re: [RFC 0/4] vgic additions for forwarded irq
Date: Mon, 24 Nov 2014 10:54:36 +0000	[thread overview]
Message-ID: <54730E6C.1040708@arm.com> (raw)
In-Reply-To: <20141124105037.GL3401@cbox>

On 24/11/14 10:50, Christoffer Dall wrote:
> On Sun, Nov 23, 2014 at 07:12:49PM +0100, Eric Auger wrote:
>> This series applies on top of "ARM: Forwarding physical
>> interrupts to a guest VM" (http://lwn.net/Articles/603514/)
>> series.
> 
> Marc and Eric,
> 
> Does it make sense to review and look at these patches given the current
> state of the forwarding patches, or should we wait until Marc respins
> that series?

I'm still in the process of respining all of this (we've had a few
iterations with tglx, but I got sidetracked with the ITS/v2m/MSI side of
things).

I'll get back onto this this week. Hopefully.

Thanks,

	M.
-- 
Jazz is not dead. It just smells funny...

  reply	other threads:[~2014-11-24 10:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-23 18:12 [RFC 0/4] vgic additions for forwarded irq Eric Auger
2014-11-23 18:12 ` [RFC 1/4] KVM: arm: vgic: fix state machine for forwarded IRQ Eric Auger
2014-11-23 18:12 ` [RFC 2/4] KVM: arm: vgic: add forwarded irq rbtree lock Eric Auger
2014-11-23 18:12 ` [RFC 3/4] KVM: arm: vgic: cleanup forwarded IRQs on destroy Eric Auger
2014-11-23 18:12 ` [RFC 4/4] KVM: arm: vgic: handle irqfd forwarded IRQ injection before vgic readiness Eric Auger
2014-11-24 10:50 ` [RFC 0/4] vgic additions for forwarded irq Christoffer Dall
2014-11-24 10:54   ` Marc Zyngier [this message]
2014-11-24 11:08     ` Eric Auger

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=54730E6C.1040708@arm.com \
    --to=marc.zyngier@arm.com \
    --cc=Will.Deacon@arm.com \
    --cc=a.motakis@virtualopensystems.com \
    --cc=a.rigo@virtualopensystems.com \
    --cc=alex.williamson@redhat.com \
    --cc=christoffer.dall@linaro.org \
    --cc=eric.auger@linaro.org \
    --cc=eric.auger@st.com \
    --cc=gleb@kernel.org \
    --cc=joel.schopp@amd.com \
    --cc=john.liuli@huawei.com \
    --cc=kim.phillips@freescale.com \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ming.lei@canon \
    --cc=patches@linaro.org \
    --cc=paulus@samba.org \
    --cc=pbonzini@redhat.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