public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Assmann <sassmann@redhat.com>
To: jbarnes@virtuousgeek.org
Cc: linux-acpi@vger.kernel.org, linux-pci@vger.kernel.org,
	JBeulich@novell.com, Olaf.Dabrunz@gmx.net, mingo@elte.hu,
	bjorn.helgaas@hp.com, tglx@linutronix.de, lenb@kernel.org
Subject: Re: [PATCH 0/5 v2] x86: boot interrupt reroute fix
Date: Tue, 11 Jan 2011 11:38:44 +0100	[thread overview]
Message-ID: <4D2C3334.8070305@redhat.com> (raw)
In-Reply-To: <20101202153344.29125.86670.sendpatchset@localhost6.localdomain6>

On 02.12.2010 16:33, Stefan Assmann wrote:
> During the 2.6.29 merge parts of e1d3a90846b40ad3160bf4b648d36c6badad39ac got
> lost because of other ACPI changes. This patchset gets the reroute code working
> again with the current ACPI code. As suggested by Ingo Molnar the missing boot
> interrupt reroute parts are re-added in separate files.
> Therefore some smaller changes to the ACPI and PCI code are necessary to allow
> the boot interrupt reroute code to access required structures and functionality.
> In detail, the reroute code requires access to:
> - struct acpi_prt_entry
> - pci_find_upstream_pcie_bridge()
> 
> Additionally to not change any information in the global acpi_prt_list it is
> desirable to have acpi_pci_irq_find_prt_entry() return a pointer to a copy of
> a struct acpi_prt_entry instead of pointer into the global acpi_prt_list. The
> callers of acpi_pci_irq_find_prt_entry() have been updated to free the
> allocated structure as well.
> 
> By request of Bjorn Helgaas I've created a bugzilla entry at
> https://bugzilla.kernel.org/show_bug.cgi?id=21882
> to gather information about the boot interrupt reroute problem.
> 
> Jesse Barnes suggested to integrate the changes through the ACPI tree.
> 
> v2:
> - split pci_find_upstream_pcie_bridge() changes into separate patches

No response from the ACPI side.

Jesse,
could you take the PCI changes (patches 3 and 4) through your tree?

  Stefan
--
Stefan Assmann         | Red Hat GmbH
Software Engineer      | Otto-Hahn-Strasse 20, 85609 Dornach
                       | HR: Amtsgericht Muenchen HRB 153243
                       | GF: Brendan Lane, Charlie Peters,
sassmann at redhat.com |     Michael Cunningham, Charles Cachera

      parent reply	other threads:[~2011-01-11 10:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-02 15:33 [PATCH 0/5 v2] x86: boot interrupt reroute fix Stefan Assmann
2010-12-02 15:33 ` [PATCH 1/5 v2] ACPI: move struct acpi_prt_entry to actbl1.h Stefan Assmann
2010-12-02 15:33 ` [PATCH 2/5 v2] ACPI: make acpi_pci_irq_find_prt_entry return a copy of a prt_entry Stefan Assmann
2010-12-02 15:33 ` [PATCH 3/5 v2] PCI: Add locking to pci_find_upstream_pcie_bridge() Stefan Assmann
2010-12-02 15:33 ` [PATCH 4/5 v2] PCI: Add header declaration for pci_find_upstream_pcie_bridge() Stefan Assmann
2010-12-02 15:34 ` [PATCH 5/5 v2] PCI, ACPI: re-add boot interrupt reroute code in separate files Stefan Assmann
2010-12-09 15:19 ` [PATCH 0/5 v2] x86: boot interrupt reroute fix Stefan Assmann
2011-01-11 10:38 ` Stefan Assmann [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=4D2C3334.8070305@redhat.com \
    --to=sassmann@redhat.com \
    --cc=JBeulich@novell.com \
    --cc=Olaf.Dabrunz@gmx.net \
    --cc=bjorn.helgaas@hp.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    /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