All of lore.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will.deacon@arm.com>
To: Andre Przywara <andre.przywara@arm.com>
Cc: "penberg@kernel.org" <penberg@kernel.org>,
	"arnd@arndb.de" <arnd@arndb.de>,
	"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>,
	Marc Zyngier <Marc.Zyngier@arm.com>
Subject: Re: [PATCH] kvmtool: don't use PCI config space IRQ line field
Date: Fri, 6 Feb 2015 18:55:27 +0000	[thread overview]
Message-ID: <20150206185527.GC24099@arm.com> (raw)
In-Reply-To: <1423064390-15269-1-git-send-email-andre.przywara@arm.com>

On Wed, Feb 04, 2015 at 03:39:50PM +0000, Andre Przywara wrote:
> In PCI config space there is an interrupt line field (offset 0x3f),
> which is used to initially communicate the IRQ line number from
> firmware to the OS. _Hardware_ should never use this information,
> as the OS is free to write any information in there.

Is this true even with probe-only? I appreciate that this isn't a BAR,
but it still feels odd for Linux to write this in that case.

Will

WARNING: multiple messages have this Message-ID (diff)
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] kvmtool: don't use PCI config space IRQ line field
Date: Fri, 6 Feb 2015 18:55:27 +0000	[thread overview]
Message-ID: <20150206185527.GC24099@arm.com> (raw)
In-Reply-To: <1423064390-15269-1-git-send-email-andre.przywara@arm.com>

On Wed, Feb 04, 2015 at 03:39:50PM +0000, Andre Przywara wrote:
> In PCI config space there is an interrupt line field (offset 0x3f),
> which is used to initially communicate the IRQ line number from
> firmware to the OS. _Hardware_ should never use this information,
> as the OS is free to write any information in there.

Is this true even with probe-only? I appreciate that this isn't a BAR,
but it still feels odd for Linux to write this in that case.

Will

  reply	other threads:[~2015-02-06 18:55 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-28 14:51 [PATCH] PCI: Fix pcibios_update_irq misuse of irq number Marc Zyngier
2015-01-28 14:51 ` Marc Zyngier
2015-01-28 15:21 ` Jiang Liu
2015-01-28 15:21   ` Jiang Liu
2015-01-28 15:27   ` Marc Zyngier
2015-01-28 15:27     ` Marc Zyngier
2015-01-28 15:27     ` Marc Zyngier
2015-01-28 15:43     ` Bjorn Helgaas
2015-01-28 15:43       ` Bjorn Helgaas
2015-01-28 15:43       ` Bjorn Helgaas
2015-02-02 16:15       ` Marc Zyngier
2015-02-02 16:15         ` Marc Zyngier
2015-02-02 16:15         ` Marc Zyngier
2015-02-02 16:22         ` Bjorn Helgaas
2015-02-02 16:22           ` Bjorn Helgaas
2015-02-02 16:22           ` Bjorn Helgaas
2015-02-02 15:57 ` Bjorn Helgaas
2015-02-02 15:57   ` Bjorn Helgaas
2015-02-02 16:06   ` Jiang Liu
2015-02-02 16:06     ` Jiang Liu
2015-02-02 16:23   ` Marc Zyngier
2015-02-02 16:23     ` Marc Zyngier
2015-02-02 16:33 ` Russell King - ARM Linux
2015-02-02 16:33   ` Russell King - ARM Linux
2015-02-02 18:08   ` Marc Zyngier
2015-02-02 18:08     ` Marc Zyngier
2015-02-02 18:08     ` Marc Zyngier
2015-02-02 18:20     ` Russell King - ARM Linux
2015-02-02 18:20       ` Russell King - ARM Linux
2015-02-02 18:20       ` Russell King - ARM Linux
2015-02-02 17:02 ` Arnd Bergmann
2015-02-02 17:02   ` Arnd Bergmann
2015-02-03 10:38   ` Marc Zyngier
2015-02-03 10:38     ` Marc Zyngier
2015-02-03 10:38     ` Marc Zyngier
2015-02-03 11:31     ` Arnd Bergmann
2015-02-03 11:31       ` Arnd Bergmann
2015-02-03 11:31       ` Arnd Bergmann
2015-02-03 11:37       ` Marc Zyngier
2015-02-03 11:37         ` Marc Zyngier
2015-02-03 11:37         ` Marc Zyngier
2015-02-03 12:57         ` Arnd Bergmann
2015-02-03 12:57           ` Arnd Bergmann
2015-02-03 12:57           ` Arnd Bergmann
2015-02-04 15:39       ` [PATCH] kvmtool: don't use PCI config space IRQ line field Andre Przywara
2015-02-04 15:39         ` Andre Przywara
2015-02-06 18:55         ` Will Deacon [this message]
2015-02-06 18:55           ` Will Deacon
2015-02-06 19:02           ` Peter Maydell
2015-02-06 19:02             ` Peter Maydell
2015-02-06 19:07             ` Will Deacon
2015-02-06 19:07               ` Will Deacon
2015-02-07 21:24               ` arnd
2015-02-07 21:24                 ` arnd at arndb.de
2015-06-04 15:20 Andre Przywara
2015-06-04 15:20 ` Andre Przywara
2015-06-05 16:41 ` Will Deacon
2015-06-05 16:41   ` Will Deacon
2015-06-15 10:45   ` Andre Przywara
2015-06-15 10:45     ` Andre Przywara
2015-06-16 17:06     ` Will Deacon
2015-06-16 17:06       ` Will Deacon
2015-06-18 17:19       ` Andre Przywara
2015-06-18 17:19         ` Andre Przywara
2015-06-29 10:10         ` Will Deacon
2015-06-29 10:10           ` Will Deacon
2015-06-29 13:48           ` Andre Przywara
2015-06-29 13:48             ` Andre Przywara

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=20150206185527.GC24099@arm.com \
    --to=will.deacon@arm.com \
    --cc=Marc.Zyngier@arm.com \
    --cc=andre.przywara@arm.com \
    --cc=arnd@arndb.de \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=penberg@kernel.org \
    /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.