On Sat, 2013-06-08 at 14:15 +0300, Artem Bityutskiy wrote:
> On Wed, 2013-05-22 at 10:43 +0100, Matt Fleming wrote:
> > From: Matt Fleming
> >
> > pcibios_add_device() assumes that the physical addresses stored in
> > setup_data are accessible via the direct kernel mapping, and that
> > calling
On Wed, 2013-05-22 at 10:43 +0100, Matt Fleming wrote:
> From: Matt Fleming
>
> pcibios_add_device() assumes that the physical addresses stored in
> setup_data are accessible via the direct kernel mapping, and that
> calling phys_to_virt() is valid. This isn't guaranteed to be true on x86
>
On Wed, 2013-05-22 at 10:43 +0100, Matt Fleming wrote:
From: Matt Fleming matt.flem...@intel.com
pcibios_add_device() assumes that the physical addresses stored in
setup_data are accessible via the direct kernel mapping, and that
calling phys_to_virt() is valid. This isn't guaranteed to be
On Sat, 2013-06-08 at 14:15 +0300, Artem Bityutskiy wrote:
On Wed, 2013-05-22 at 10:43 +0100, Matt Fleming wrote:
From: Matt Fleming matt.flem...@intel.com
pcibios_add_device() assumes that the physical addresses stored in
setup_data are accessible via the direct kernel mapping, and that
4533162487fa1e4bc23877a8a502 Mon Sep 17 00:00:00 2001
> From: Matt Fleming
> Date: Wed, 22 May 2013 09:56:23 +0100
> Subject: [PATCH] x86/PCI: setup data may be in highmem
>
> pcibios_add_device() assumes that the physical addresses stored in
> setup_data are accessible via the
I've seen. I've included the new patch below. Would you prefer a
proper submission?
---
>From 7a82fbe1d0c74533162487fa1e4bc23877a8a502 Mon Sep 17 00:00:00 2001
From: Matt Fleming
Date: Wed, 22 May 2013 09:56:23 +0100
Subject: [PATCH] x86/PCI: setup data may be in highmem
pcibios_add_devi
. I've included the new patch below. Would you prefer a
proper submission?
---
From 7a82fbe1d0c74533162487fa1e4bc23877a8a502 Mon Sep 17 00:00:00 2001
From: Matt Fleming matt.flem...@intel.com
Date: Wed, 22 May 2013 09:56:23 +0100
Subject: [PATCH] x86/PCI: setup data may be in highmem
Mon Sep 17 00:00:00 2001
From: Matt Fleming matt.flem...@intel.com
Date: Wed, 22 May 2013 09:56:23 +0100
Subject: [PATCH] x86/PCI: setup data may be in highmem
pcibios_add_device() assumes that the physical addresses stored in
setup_data are accessible via the direct kernel mapping
On Tue, May 28, 2013 at 10:48 AM, Matthew Garrett wrote:
> On Tue, May 28, 2013 at 10:31:51AM -0600, Bjorn Helgaas wrote:
>> On Tue, May 28, 2013 at 5:36 AM, Matt Fleming wrote:
>> > On Fri, 24 May, at 08:38:10AM, Bjorn Helgaas wrote:
>> >> pcibios_add_device() is mostly called at boot-time,
On Tue, May 28, 2013 at 10:31:51AM -0600, Bjorn Helgaas wrote:
> On Tue, May 28, 2013 at 5:36 AM, Matt Fleming wrote:
> > On Fri, 24 May, at 08:38:10AM, Bjorn Helgaas wrote:
> >> pcibios_add_device() is mostly called at boot-time, when
> >> early_ioremap() probably works well. But it's also
On Tue, May 28, 2013 at 5:36 AM, Matt Fleming wrote:
> On Fri, 24 May, at 08:38:10AM, Bjorn Helgaas wrote:
>> pcibios_add_device() is mostly called at boot-time, when
>> early_ioremap() probably works well. But it's also called when we
>> hot-add devices later, and it looks like early_ioremap()
On Fri, 24 May, at 08:38:10AM, Bjorn Helgaas wrote:
> pcibios_add_device() is mostly called at boot-time, when
> early_ioremap() probably works well. But it's also called when we
> hot-add devices later, and it looks like early_ioremap() will then
> generate warnings because "system_state !=
On Fri, 24 May, at 08:38:10AM, Bjorn Helgaas wrote:
pcibios_add_device() is mostly called at boot-time, when
early_ioremap() probably works well. But it's also called when we
hot-add devices later, and it looks like early_ioremap() will then
generate warnings because system_state !=
On Tue, May 28, 2013 at 5:36 AM, Matt Fleming m...@console-pimps.org wrote:
On Fri, 24 May, at 08:38:10AM, Bjorn Helgaas wrote:
pcibios_add_device() is mostly called at boot-time, when
early_ioremap() probably works well. But it's also called when we
hot-add devices later, and it looks like
On Tue, May 28, 2013 at 10:31:51AM -0600, Bjorn Helgaas wrote:
On Tue, May 28, 2013 at 5:36 AM, Matt Fleming m...@console-pimps.org wrote:
On Fri, 24 May, at 08:38:10AM, Bjorn Helgaas wrote:
pcibios_add_device() is mostly called at boot-time, when
early_ioremap() probably works well. But
On Tue, May 28, 2013 at 10:48 AM, Matthew Garrett mj...@srcf.ucam.org wrote:
On Tue, May 28, 2013 at 10:31:51AM -0600, Bjorn Helgaas wrote:
On Tue, May 28, 2013 at 5:36 AM, Matt Fleming m...@console-pimps.org wrote:
On Fri, 24 May, at 08:38:10AM, Bjorn Helgaas wrote:
pcibios_add_device() is
On Wed, May 22, 2013 at 3:43 AM, Matt Fleming wrote:
> From: Matt Fleming
>
> pcibios_add_device() assumes that the physical addresses stored in
> setup_data are accessible via the direct kernel mapping, and that
> calling phys_to_virt() is valid. This isn't guaranteed to be true on x86
> where
On Wed, May 22, 2013 at 3:43 AM, Matt Fleming m...@console-pimps.org wrote:
From: Matt Fleming matt.flem...@intel.com
pcibios_add_device() assumes that the physical addresses stored in
setup_data are accessible via the direct kernel mapping, and that
calling phys_to_virt() is valid. This
On 05/22/2013 02:43 AM, Matt Fleming wrote:
> From: Matt Fleming
>
> pcibios_add_device() assumes that the physical addresses stored in
> setup_data are accessible via the direct kernel mapping, and that
> calling phys_to_virt() is valid. This isn't guaranteed to be true on x86
> where the
On 05/22/2013 02:43 AM, Matt Fleming wrote:
From: Matt Fleming matt.flem...@intel.com
pcibios_add_device() assumes that the physical addresses stored in
setup_data are accessible via the direct kernel mapping, and that
calling phys_to_virt() is valid. This isn't guaranteed to be true on x86
From: Matt Fleming
pcibios_add_device() assumes that the physical addresses stored in
setup_data are accessible via the direct kernel mapping, and that
calling phys_to_virt() is valid. This isn't guaranteed to be true on x86
where the direct mapping range is much smaller than on x86-64.
Calling
From: Matt Fleming matt.flem...@intel.com
pcibios_add_device() assumes that the physical addresses stored in
setup_data are accessible via the direct kernel mapping, and that
calling phys_to_virt() is valid. This isn't guaranteed to be true on x86
where the direct mapping range is much smaller
22 matches
Mail list logo
