mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] xen: do not map the same GSI twice
Date: Mon, 21 May 2012 19:02:12 +0100	[thread overview]
Message-ID: <alpine.DEB.2.00.1205211901220.26786@kaball-desktop> (raw)
In-Reply-To: <20120521175142.GA13990@phenom.dumpdata.com>

On Mon, 21 May 2012, Konrad Rzeszutek Wilk wrote:
> On Mon, May 21, 2012 at 06:47:44PM +0100, Stefano Stabellini wrote:
> > On Mon, 21 May 2012, Konrad Rzeszutek Wilk wrote:
> > > On Mon, May 21, 2012 at 04:54:10PM +0100, Stefano Stabellini wrote:
> > > > PV on HVM guests map GSIs into event channels; at restore time the
> > > > event channels are resumed by restore_pirqs.
> > > > Device drivers might try to register the same GSI again through ACPI at
> > > > restore time, but the GSI has already been mapped and bound by
> > > > restore_pirqs.
> > > 
> > > Which means... what kind of error do we get without this patch?
> > 
> > Xen would print:
> > 
> > (XEN) irq.c:2235: dom4: pirq 23 or emuirq 28 already mapped
> > 
> > and waste a pirq
> 
> OK. This sounds like it has been a bug since ..oh forever then?
> 

Yes. It only showed up since the ata_piix driver started registering the
GSI again on resume (I don't know when this behavior started exactly).

      reply	other threads:[~2012-05-21 18:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-21 15:54 Stefano Stabellini
2012-05-21 17:27 ` Konrad Rzeszutek Wilk
2012-05-21 17:47   ` Stefano Stabellini
2012-05-21 17:51     ` Konrad Rzeszutek Wilk
2012-05-21 18:02       ` Stefano Stabellini [this message]

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=alpine.DEB.2.00.1205211901220.26786@kaball-desktop \
    --to=stefano.stabellini@eu.citrix.com \
    --cc=konrad.wilk@oracle.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

all inboxes | Powered by JetHome®