diff for duplicates of <20130929105015.GQ17294@redhat.com> diff --git a/a/1.txt b/N1/1.txt index 482e061..31d0762 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -6,7 +6,7 @@ On Thu, Sep 26, 2013 at 10:00:59AM +1000, Paul Mackerras wrote: > > > > > This implements a simple way to express the case of IRQ routing where > > > > > there is one in-kernel PIC and the system interrupts (GSIs) are routed > > > > > 1-1 to the corresponding pins of the PIC. This is expressed by having -> > > > > kvm->irq_routing = NULL with a skeleton irq routing entry in the new +> > > > > kvm->irq_routing == NULL with a skeleton irq routing entry in the new > > > > > kvm->default_irq_route field. > > > > > > > > > > This provides a convenient way to provide backwards compatibility when @@ -14,7 +14,7 @@ On Thu, Sep 26, 2013 at 10:00:59AM +1000, Paul Mackerras wrote: > > > > > XICS emulation on powerpc. > > > > > > > > > Why not create simple 1-1 irq routing table? It will take a little bit -> > > > more memory, but there will be no need for kvm->irq_routing = NULL +> > > > more memory, but there will be no need for kvm->irq_routing == NULL > > > > special handling. > > > > > > The short answer is that userspace wants to use interrupt source diff --git a/a/content_digest b/N1/content_digest index e88f0bc..9208bed 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -5,7 +5,7 @@ "ref\020130926000059.GB2844@iris.ozlabs.ibm.com\0" "From\0Gleb Natapov <gleb@redhat.com>\0" "Subject\0Re: [PATCH 1/2] KVM: Implement default IRQ routing\0" - "Date\0Sun, 29 Sep 2013 10:50:15 +0000\0" + "Date\0Sun, 29 Sep 2013 13:50:15 +0300\0" "To\0Paul Mackerras <paulus@samba.org>\0" "Cc\0kvm@vger.kernel.org" kvm-ppc@vger.kernel.org @@ -21,7 +21,7 @@ "> > > > > This implements a simple way to express the case of IRQ routing where\n" "> > > > > there is one in-kernel PIC and the system interrupts (GSIs) are routed\n" "> > > > > 1-1 to the corresponding pins of the PIC. This is expressed by having\n" - "> > > > > kvm->irq_routing = NULL with a skeleton irq routing entry in the new\n" + "> > > > > kvm->irq_routing == NULL with a skeleton irq routing entry in the new\n" "> > > > > kvm->default_irq_route field.\n" "> > > > > \n" "> > > > > This provides a convenient way to provide backwards compatibility when\n" @@ -29,7 +29,7 @@ "> > > > > XICS emulation on powerpc.\n" "> > > > > \n" "> > > > Why not create simple 1-1 irq routing table? It will take a little bit\n" - "> > > > more memory, but there will be no need for kvm->irq_routing = NULL\n" + "> > > > more memory, but there will be no need for kvm->irq_routing == NULL\n" "> > > > special handling.\n" "> > > \n" "> > > The short answer is that userspace wants to use interrupt source\n" @@ -84,4 +84,4 @@ "--\n" "\t\t\tGleb." -b79cf4e9ae132a2830d664c9d5e57d6c046b4657356bc04a3887b7d10a1b3a2b +d27fe5d838003a0f8b87521bed9dbb96d26c6765cb049a24ec610d9328769dbf
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.