ons
didn't initialize high part of 64bit BAR.
The patch is tested on Linux 2.6.18 - 3.1.0 and Windows 2008 Server
Signed-off-by: Alexey Korolev
---
hw/pci.c | 45 +
hw/pci.h |7 +++
2 files changed, 52 insertions(+), 0 deletions(-)
d
Hi Alex and Michael
>> For testing, I applied the following patch to qemu,
>> converting msix bar to 64 bit.
>> Guest did not seem to crash.
>> I booted Fedora Live CD 32 bit guest on a 32 bit host
>> to level 3 without crash, and verified that
>> the BAR is a 64 bit one, and that I got assigned an
On 26/01/12 01:51, Michael S. Tsirkin wrote:
> On Wed, Jan 25, 2012 at 06:46:03PM +1300, Alexey Korolev wrote:
>> Hi,
>> In this post
>> http://lists.gnu.org/archive/html/qemu-devel/2011-12/msg03171.html I've
>> mentioned about the issues when 64Bit PCI BAR is pr
On 27/01/12 03:36, Michael S. Tsirkin wrote:
> On Thu, Jan 26, 2012 at 03:52:27PM +0200, Avi Kivity wrote:
>> On 01/26/2012 11:14 AM, Michael S. Tsirkin wrote:
>>> On Wed, Jan 25, 2012 at 06:46:03PM +1300, Alexey Korolev wrote:
>>>> Hi,
>>>> In this p
On 27/01/12 04:12, Avi Kivity wrote:
> On 01/26/2012 04:36 PM, Michael S. Tsirkin wrote:
>> On Thu, Jan 26, 2012 at 03:52:27PM +0200, Avi Kivity wrote:
>>> On 01/26/2012 11:14 AM, Michael S. Tsirkin wrote:
>>>> On Wed, Jan 25, 2012 at 06:46:03PM +1300, Alexey Koro
On 31/01/12 22:43, Avi Kivity wrote:
> On 01/31/2012 11:40 AM, Avi Kivity wrote:
>> On 01/27/2012 06:42 AM, Alexey Korolev wrote:
>>> On 27/01/12 04:12, Avi Kivity wrote:
>>>> On 01/26/2012 04:36 PM, Michael S. Tsirkin wrote:
>>>>> On Thu, Jan 2
On 01/02/12 20:04, Michael S. Tsirkin wrote:
> On Wed, Feb 01, 2012 at 06:44:42PM +1300, Alexey Korolev wrote:
>> On 31/01/12 22:43, Avi Kivity wrote:
>>> On 01/31/2012 11:40 AM, Avi Kivity wrote:
>>>> On 01/27/2012 06:42 AM, Alexey Korolev wrote:
>>>
Hi all,
I had qemu 1.2.0 crash when using ivshmem driver with 64bit PCI support
enabled. The qemu process is terminated at a very early stage of
Linux boot up. Here is the qemu command line:
LC_ALL=C
PATH=/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/u
Hi Gerd,
> Hi,
>
>> And qemu error output is:
>> qemu: /home/akorolev/qemu-kvm/exec.c:2255: register_subpage: Assertion
>> `existing->mr->subpage || existing->mr == &io_mem_unassigned' failed.
>>
>> Guest OS is Centos 5.5 and log is pretty boring, as qemu crashes before
>> Linux can report an i
On 06/12/12 09:23, Alexey Korolev wrote:
> Hi Gerd,
>> Hi,
>>
>>> And qemu error output is:
>>> qemu: /home/akorolev/qemu-kvm/exec.c:2255: register_subpage: Assertion
>>> `existing->mr->subpage || existing->mr == &io_mem_unassigned&#x
I tried the head today.
Qemu crashes in the same way as before.
> Hi,
>
>> And qemu error output is:
>> qemu: /home/akorolev/qemu-kvm/exec.c:2255: register_subpage: Assertion
>> `existing->mr->subpage || existing->mr == &io_mem_unassigned' failed.
>>
>> Guest OS is Centos 5.5 and log is pretty
On 06/12/12 20:45, Gerd Hoffmann wrote:
> On 12/06/12 05:09, Alexey Korolev wrote:
>> I tried the head today.
>> Qemu crashes in the same way as before.
> Hmm. Doesn't reproduce here (using RHEL-5 as guest, although it is 5.8
> so more recent than your centos 5.5).
&g
Hi,
>> It is a 64bit guest OS.
>> I've upgraded to RHEL 5.8 and still have the same problem.
> My rhel5 is 32bit.
>
>> Could you please send me a qemu command line you are running?
> qemu-default -m 512 -hda /vmdisk/guests/rhel5.img -device
> ivshmem,size=128M,shm=ivshmem.root
Could you please set
On 10/12/12 20:22, Gerd Hoffmann wrote:
> On 12/10/12 03:05, Alexey Korolev wrote:
>> Hi,
>>>> It is a 64bit guest OS.
>>>> I've upgraded to RHEL 5.8 and still have the same problem.
>>> My rhel5 is 32bit.
>>>
>>>> Could you ple
Sometime ago I reported an issue about guest OS hang when 64bit BAR present.
http://lists.gnu.org/archive/html/qemu-devel/2012-01/msg03189.html
http://lists.gnu.org/archive/html/qemu-devel/2012-12/msg00413.html
Some more investigation has been done, so in this post I'll try to explain why
it happ
rule that the
regions which should not be overlapped are added to the
view first (i.e. having highest priority). The patch
also corrects ivshmem bar resource to be overlapable
which is the default for PCI BARs
Signed-off-by: Alexey Korolev
---
hw/ivshmem.c |2 +-
memory.c | 15
> On Wed, Feb 13, 2013 at 11:34:52AM +0100, Jan Kiszka wrote:
>> On 2013-02-13 11:24, Michael S. Tsirkin wrote:
>>> On Wed, Feb 13, 2013 at 06:06:37PM +1300, Alexey Korolev wrote:
>>>> Sometime ago I reported an issue about guest OS hang when 64bit BAR
>>&
On 13/02/13 23:26, Michael S. Tsirkin wrote:
> On Wed, Feb 13, 2013 at 06:14:33PM +1300, Alexey Korolev wrote:
>> At the moment may_overlap flag of MemoryRegion structure
>> is ignored by the address range assignment process.
>> This may lead to guest OS hangs if critical
priorities can take values
0,1,2 or even 1000.
This patch removes these drawbacks and introduces a predefined set
of priorities for MemoryRegion.
This code does not affect the exisiting memory topology build process,
so does not cause any issues related to change of regions visibility.
Alexey
have exclusive priority.
Since may_overlap is abandoned, memory_region_add_subregion and
memory_region_add_subregion_common become equvalent so
memory_region_add_subregion_common is removed.
Signed-off-by: Alexey Korolev
---
include/exec/memory.h |1 -
memory.c | 21
optionally use
memory_region_set_priority() to change priority from the default.
This patch adds predefined priority values in memory.h. Priority can take
one of 4 possible values: low (default), medium, high and exclusive
(highest).
Signed-off-by: Alexey Korolev
---
hw/armv7m_nvic.c |4
Updated documentation about overlapping memory regions and priority
to match the latest implementation.
Signed-off-by: Alexey Korolev
---
docs/memory.txt | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/docs/memory.txt b/docs/memory.txt
index 5bbee8e..37ebeb8
On Wed, Feb 20, 2013 at 4:20 AM, Michael S. Tsirkin wrote:
> apic overlaps PCI space. On real hardware it has
> higher priority, emulate this correctly.
>
> This should addresses the following issue:
>
>> Subject: Re: [BUG] Guest OS hangs on boot when 64bit BAR present
>> (kvm-apic-msi resource c
-apic memory region, so it is
never pushed out by PCI devices. The patch is quite safe as it does not
touch memory manager.
Signed-off-by: Alexey Korolev
Signed-off-by: Michael S. Tsirkin
---
hw/sysbus.c | 27 +++
hw/sysbus.h |2 ++
target-i386/cpu.c |3
Unfortunately I cannot even guess what is happening with kvm-apic-msi, or why
it does not tolerate overlaps. This is actually a still open qestion.
>>
>> This patch raises the priority of the kvm-apic memory region, so it is
>> never pushed out by PCI devices. The patch is quite safe a
Hi,
There were a number of requests about support of 64bit PCI BAR allocations.
Also we have observed the issue on guests with older linux version
(2.6.18): if we
have a 64bit BAR allocated within first 4GB, the OS may hang during
start process.
(I guess it is an OS bug, but we need to take c
x27;t mind.
Signed-off-by: Alexey Korolev
Signed-off-by: Michael S. Tsirkin
---
src/acpi-dsdt.dsl |7 +
src/acpi-dsdt.hex | 66
+
src/config.h |2 +
3 files changed, 65 insertions(+), 10 deletions(-)
diff --git a/src/acpi-dsdt
ation, the
bridges can describe 64bit ranges for prefetchable type of memory only.
So it's very
unlikely that devices exporting 64bit non-prefetchable BARs. Anyway this
code will work
with 64bit non-prefetchable BARs unless the PCI device is not behind the
secondary bus.
Signed-off-by:
-off-by: Alexey Korolev
---
src/pciinit.c | 69 +++-
1 files changed, 48 insertions(+), 21 deletions(-)
diff --git a/src/pciinit.c b/src/pciinit.c
index a574e38..92942d5 100644
--- a/src/pciinit.c
+++ b/src/pciinit.c
@@ -17,6 +17,7 @@
#define
I hate thunderbird. Will resend the patches tomorrow.
>+pci_config_writel(bdf, PCI_PREF_BASE_UPPER32, base>> 32);
On 29/12/11 00:30, Michael S. Tsirkin wrote:
On Wed, Dec 28, 2011 at 06:26:05PM +1300, Alexey Korolev wrote:
This patch adds PCI_REGION_TYPE_PREFMEM_64 region type and modifies types of
variables to make it possible to work with 64 bit addresses.
Why I've added just one region
On 29/12/11 15:56, Kevin O'Connor wrote:
On Wed, Dec 28, 2011 at 06:26:05PM +1300, Alexey Korolev wrote:
This patch adds PCI_REGION_TYPE_PREFMEM_64 region type and modifies types of
variables to make it possible to work with 64 bit addresses.
Why I've added just one r
@@ -69,6 +72,8 @@ static enum pci_region_type pci_addr_to_type(u32 addr)
{
if (addr& PCI_BASE_ADDRESS_SPACE_IO)
return PCI_REGION_TYPE_IO;
+if (addr& PCI_BASE_ADDRESS_MEM_TYPE_64)
+return PCI_REGION_TYPE_PREFMEM_64;
This seems dangerous - a 64bit bar can be non-p
On 29/12/11 00:43, Michael S. Tsirkin wrote:
On Wed, Dec 28, 2011 at 06:35:55PM +1300, Alexey Korolev wrote:
All devices behind a bridge need to have all their regions consecutive and
not overlapping with all the normal memory ranges.
Since prefetchable memory is described by one record, we
On 29/12/11 00:43, Michael S. Tsirkin wrote:
On Wed, Dec 28, 2011 at 06:35:55PM +1300, Alexey Korolev wrote:
All devices behind a bridge need to have all their regions consecutive and
not overlapping with all the normal memory ranges.
Since prefetchable memory is described by one record, we
>>
> Patches have been tested on several configurations which includes
>> linux 2.6.18 - 3.0 &
>> windows 2008. Everything works quite well.
>Which qemu version did you use?
I tried both 0.15 and 1.0
On 30/12/11 05:21, Michael S. Tsirkin wrote:
On Thu, Dec 29, 2011 at 09:20:00AM +, Alexey Korolev wrote:
Patches have been tested on several configurations which includes
linux 2.6.18 - 3.0&
windows 2008. Everything works quite well.
Which qemu version did you use?
I tried both 0.15
On 30/12/11 05:18, Michael S. Tsirkin wrote:
On Thu, Dec 29, 2011 at 06:40:26PM +1300, Alexey Korolev wrote:
On 29/12/11 00:43, Michael S. Tsirkin wrote:
On Wed, Dec 28, 2011 at 06:35:55PM +1300, Alexey Korolev wrote:
All devices behind a bridge need to have all their regions consecutive and
On 30/12/11 05:21, Michael S. Tsirkin wrote:
On Thu, Dec 29, 2011 at 06:41:36PM +1300, Alexey Korolev wrote:
Can't figure this out. What does this do?
Bios will panic if it founds prefmem BARs in both 32bit and 64bit areas.
That's not good, it's a legal configuration.
To b
On 30/12/11 05:21, Michael S. Tsirkin wrote:
On Thu, Dec 29, 2011 at 06:41:36PM +1300, Alexey Korolev wrote:
Can't figure this out. What does this do?
Bios will panic if it founds prefmem BARs in both 32bit and 64bit areas.
That's not good, it's a legal configuration.
To b
>> >There are two main things we can do:
>> >1. Make the 64 bit device only use the low 32 bit
>> It was my first implementation. Unfortunately older versions of
>> Linux (Like 2.6.18) hang during startup with this.
>> As far as I remember it was qemu-0.15 so may be 1.0 have no such an
>> issue.
Hi,
This patch series redesigns the existing pciinit.c code and introduces
linked list operations.
Changes are more about structures definitions rather than functionality.
There are no more arrays of bases and counts in new implementation. The
new implementation is based on dynamic allocation of p
This linked list implementation is partially based on kernel code. So it
should be quite stable :)
Signed-off-by: Alexey Korolev
---
src/util.h | 32
1 files changed, 32 insertions(+), 0 deletions(-)
diff --git a/src/util.h b/src/util.h
index 70d3c4c..d1002a9
Added pci_region_entry structure and list operations to pciinit.c
List is filled with entries during pci_check_devices.
List is used just for printing space allocation if we were using lists.
Next step will resource allocation using mapping functions.
Signed-off-by: Alexey Korolev
---
src
-by: Alexey Korolev
---
src/pciinit.c | 106 +
1 files changed, 46 insertions(+), 60 deletions(-)
diff --git a/src/pciinit.c b/src/pciinit.c
index 2bf5473..f766a75 100644
--- a/src/pciinit.c
+++ b/src/pciinit.c
@@ -12,9 +12,8 @@
#include
This patch deletes array based code need for resource assignment.
The patches 3 and 4 are split just for better readability.
Signed-off-by: Alexey Korolev
---
src/pciinit.c | 109 +
1 files changed, 1 insertions(+), 108 deletions
The size element of pci_bus->r structure is no longer need as the
information about bridge region size is stored in pci_region_entry
structure.
Signed-off-by: Alexey Korolev
---
src/pciinit.c | 21 +
1 files changed, 9 insertions(+), 12 deletions(-)
diff --git a/
This patch simplifies a bit complicated code in pmm.c and stack.c
Signed-off-by: Alexey Korolev
---
src/pmm.c| 29 +
src/stacks.c |8 ++--
2 files changed, 11 insertions(+), 26 deletions(-)
diff --git a/src/pmm.c b/src/pmm.c
index c649fd8..996981c
On 14/03/12 13:48, Kevin O'Connor wrote:
> On Tue, Mar 13, 2012 at 05:45:19PM +1300, Alexey Korolev wrote:
>> Added pci_region_entry structure and list operations to pciinit.c
>> List is filled with entries during pci_check_devices.
>> List is used just for printing s
On 16/03/12 13:55, Kevin O'Connor wrote:
> On Thu, Mar 15, 2012 at 04:29:30PM +1300, Alexey Korolev wrote:
>> On 14/03/12 13:48, Kevin O'Connor wrote:
>>> On Tue, Mar 13, 2012 at 05:45:19PM +1300, Alexey Korolev wrote:
>>>> Added pci_region_entry st
> Hi,
>
> There is a typo in i440FX init code. This is causing problems when
> somebody wants to access 64bit PCI range.
>
>
> Signed-off-by: Alexey Korolev
> ---
>
> hw/piix_pci.c |2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> dif
> On Wed, Feb 29, 2012 at 02:35:14PM +1300, Alexey Korolev wrote:
> I've fixed the commit message and applied.
Thank you!
> How does one trigger the problem?
> I'd like to know so I can test for it.
The i440fx_init() function is called from pc_init code.
The call lo
Hi,
This patch series redesigns the existing pciinit.c code and introduces
linked list operations.
Changes are more about structures definitions rather than functionality.
There are no more arrays of bases and counts in new implementation. The
new implementation is based on dynamic allocation of p
This linked list implementation is partially based on kernel code. So it
should be quite stable
Signed-off-by: Alexey Korolev
---
src/util.h | 21 +
1 files changed, 21 insertions(+), 0 deletions(-)
diff --git a/src/util.h b/src/util.h
index 70d3c4c..17df3cf 100644
--- a
In this patch the pci_region_entry structure is introduced.
The pci_device->bars are removed. The information from
pci_region_entry is used to program pci bars.
Signed-off-by: Alexey Korolev
---
src/pci.h |5 --
src/pciinit.c |
In this patch instead of array based resource allocation approach
we calculate resource addresses linked lists of pci_region_entry structures.
Signed-off-by: Alexey Korolev
---
src/pciinit.c | 179 -
1 files changed, 50 insertions
The 'size' element of pci_bus->r structure is no longer need
as the information about bridge region size is already stored in
pci_region_entry structure.
Signed-off-by: Alexey Korolev
---
src/pciinit.c | 21 +
1 files changed, 9 insertions(+), 12 deletions(-)
>> This linked list implementation is partially based on kernel code. So it
>> should be quite stable
> How about just copying the file?
>
> I've used the linux kernel list implementation elsewhere too and it
> worked just fine with only minor tweaks (remove some likely()/unlikely()
> macros IIRC)
Hi Kevin,
Thank you for the patches!
I've created a diff of final version of your changes over mine, to make it
clear what has changed.
Rather than including the complete diff, I've just left relevant parts and
added comments.
--- a/src/pciinit.c +++ b/src/pciinit.c@@ -12,8 +12,9 @@
@
On 04/04/12 15:31, Kevin O'Connor wrote:
> Agreed - the only thing it does is force a minimum size for memory bars as
> you pointed out in a previous email. As above, I did play with
> this a little more on Sunday. I also added in two patches from Gerd's series
> and made alignment handling more
On 12/04/12 15:15, Kevin O'Connor wrote:
>
> This was also me playing with one of Gerd's patches. It just makes
> the bar read/write code 64bit aware. It doesn't actually program
> them. The logic to do real 64bit allocations would require list
> merging. Is this something you have looked at?
R
[...]
>> [Patch 5]
>> Track-alignment-explicitly
>> Almost the same as the previous, just changed priority from r->align to
>> r->sum when setting start address of root regions.
>>
>> I guess there are more chances to fit memory regions if we try place regions
>> with higher r->sum like it was b
06-pciinit-bridges-can-have-two-regions-too.patch
0007-pciinit-Switch-to-64bit-variable-types.patch
Alexey Korolev (6):
0003-pciinit-Remove-size-element-from-pci_bus-r-structure.patch
0008-pciinit-Add-pci_region-structure.patch
0009-pciinit-64bit-capability-discovery-for-pci-bridges.patch
0010-Do-not
The pci_region_entry structure is introduced.
The pci_device->bars are removed. The information from
pci_region_entry is used to program pci bars.
Signed-off-by: Alexey Korolev
Signed-off-by: Kevin O'Connor
---
src/pci.h |5 --
src/pciinit.
Perform bus bar assignment at same time as normal bar assignment
Signed-off-by: Kevin O'Connor
Signed-off-by: Alexey Korolev
---
src/pciinit.c | 53 ++---
1 files changed, 18 insertions(+), 35 deletions(-)
diff --git a/src/pciinit.c
The 'size' element of pci_bus->r structure is no
longer need as the information about bridge region
size is already stored in pci_region_entry structure.
Signed-off-by: Alexey Korolev
Signed-off-by: Kevin O'Connor
---
src/pciinit.c | 20
1 files cha
Use sorted order allocation scheme instead of
array based count scheme.
Signed-off-by: Alexey Korolev
Signed-off-by: Kevin O'Connor
---
src/pciinit.c | 71 +---
1 files changed, 7 insertions(+), 64 deletions(-)
diff --git a/src/pciini
Don't round up bridge regions to the next highest size - instead track
alignment explicitly. This should improve the memory layout for
bridge regions.
Also, unused bridge regions will no longer be allocated any space.
Signed-off-by: Kevin O'Connor
---
src/pciinit.c | 41 ++---
Patch takes into account PCI bar and ROM regions of PCI bridges
Original patch by: Gerd Hoffmann
Signed-off-by: Kevin O'Connor
Signed-off-by: Alexey Korolev
---
src/pci.h |1 +
src/pciinit.c |8 +---
2 files changed, 6 insertions(+), 3 deletions(-)
diff --git a/src/pc
Switch to 64bit variable types.
Add parsing 64bit bars.
Original patch by: Gerd Hoffmann
Signed-off-by: Kevin O'Connor
---
src/pciinit.c | 116 ++---
1 files changed, 61 insertions(+), 55 deletions(-)
diff --git a/src/pciinit.c b/src/pciini
The pci_region structure is added.
Move setting of bus base address to pci_region_map_entries.
Signed-off-by: Alexey Korolev
---
src/pciinit.c | 50 --
1 files changed, 28 insertions(+), 22 deletions(-)
diff --git a/src/pciinit.c b/src
Add discovery if bridge region is 64bit is capable.
Signed-off-by: Alexey Korolev
---
src/pciinit.c | 26 +-
1 files changed, 25 insertions(+), 1 deletions(-)
diff --git a/src/pciinit.c b/src/pciinit.c
index f185cbd..0d66dbe 100644
--- a/src/pciinit.c
+++ b/src
Do not store pci region stats - instead calulate the
sum and alignment on demand.
Signed-off-by: Alexey Korolev
---
src/pciinit.c | 57
+++--
1 files changed, 35 insertions(+), 22 deletions(-)
diff --git a/src/pciinit.c b/src/pciinit.c
Do not store pci region stats - instead calulate the
sum and alignment on demand.
Signed-off-by: Alexey Korolev
---
src/pciinit.c | 57 +++--
1 files changed, 35 insertions(+), 22 deletions(-)
diff --git a/src/pciinit.c b/src/pciinit.c
Migrate 64bit entries to 64bit pci regions if they do
not fit in 32bit range.
Signed-off-by: Alexey Korolev
---
src/config.h |2 ++
src/pciinit.c | 50 ++
2 files changed, 48 insertions(+), 4 deletions(-)
diff --git a/src/config.h b/src
This patch solves issues on Windows guests, when 64bit
BAR's are present. It is also helpful on Linux guests
when use_crs kernel boot option is set.
Signed-off-by: Alexey Korolev
Signed-off-by: Michael S. Tsirkin
---
src/acpi-dsdt.dsl |7 +
src/acpi-dsdt.hex |
A flowed text. Please apply another [10/12] in this series.
On Tue, 2012-04-24 at 18:23 +1200, Alexey Korolev wrote:
> Do not store pci region stats - instead calulate the
> sum and alignment on demand.
>
> Signed-off-by: Alexey Korolev
> ---
> sr
On 24/04/12 18:56, Gerd Hoffmann wrote:
> On 04/24/12 08:17, Alexey Korolev wrote:
>> Don't round up bridge regions to the next highest size - instead track
>> alignment explicitly. This should improve the memory layout for
>> bridge regions.
> This one got mangl
On 25/04/12 13:48, Kevin O'Connor wrote:
> On Tue, Apr 24, 2012 at 06:25:39PM +1200, Alexey Korolev wrote:
>> Migrate 64bit entries to 64bit pci regions if they do
>> not fit in 32bit range.
> [...]
>> +static void pci_region_migrate_64bit_en
Hi,
There is a typo in i440FX init code. This is causing problems when
somebody wants to access 64bit PCI range.
Signed-off-by: Alexey Korolev
---
hw/piix_pci.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/hw/piix_pci.c b/hw/piix_pci.c
index 3ed3d90..aab8188
Hi,
This patch series enables 64bit BAR support in seabios.
It has a bit different approach for resources accounting, We did this
because we wanted:
a) Provide 64bit bar support for PCI BARs and bridges with 64bit memory
window.
b) Allow migration to 64bit bit ranges if we did not fit into 32bit
build topology and migrate entries if necessary.
Signed-off-by: Alexey Korolev
---
src/pci.h |6 --
src/pciinit.c | 37 ++---
2 files changed, 22 insertions(+), 21 deletions(-)
diff --git a/src/pci.h b/src/pci.h
index a2a5a4c..8fa064f 100644
--- a
: Alexey Korolev
---
src/pciinit.c | 132 +++--
1 files changed, 91 insertions(+), 41 deletions(-)
diff --git a/src/pciinit.c b/src/pciinit.c
index 2e5416c..dbfa4f2 100644
--- a/src/pciinit.c
+++ b/src/pciinit.c
@@ -51,33 +51,30 @@ struct
pci_bios_fill_regions() scans pci_regions in reverse order
to calculate size of pci_region_entries belonging to a bridge.
Signed-off-by: Alexey Korolev
---
src/pciinit.c | 103 ++---
1 files changed, 98 insertions(+), 5 deletions(-)
diff --git a
provides
a pci_region for downstream devices, we set base address of the region the
entry provides.
3. Delete entry.
Signed-off-by: Alexey Korolev
---
src/config.h |2 +
src/pciinit.c | 123 -
2 files changed, 124 insertions(+), 1
Delete old code.
Signed-off-by: Alexey Korolev
---
src/pciinit.c | 212 -
1 files changed, 0 insertions(+), 212 deletions(-)
diff --git a/src/pciinit.c b/src/pciinit.c
index 0fba130..9c41e3c 100644
--- a/src/pciinit.c
+++ b/src/pciinit.c
This patch was originally proposed by Michael, to solve issues I've seen
on Windows guests, when 64bit BAR's are present.
This patch also might be helpful on Linux guests when use_crs kernel
boot option is set.
Signed-off-by: Alexey Korolev
Signed-off-by: Michael S. Tsirkin
---
Hi,
What is your setup?
I want to reproduce this case
>> a) Provide 64bit bar support for PCI BARs and bridges with 64bit memory
>> window.
> Bridge support seems to be completely untested. /me has a test setup
> using mst's bridge patches which looks like this:
>
> [root@fedora ~]# lspci -tv
> -[
On 01/03/12 22:22, Gerd Hoffmann wrote:
> On 03/01/12 07:57, Alexey Korolev wrote:
>> In pci_bios_map_regions() we try to reserve memory for
>> all entries of root bus regions.
>> If pci_bios_init_root_regions() fails - e.g no enough space, we create two
>> new pci_
On 02/03/12 20:21, Gerd Hoffmann wrote:
> On 03/01/12 23:01, Alexey Korolev wrote:
>> On 01/03/12 22:22, Gerd Hoffmann wrote:
>>> On 03/01/12 07:57, Alexey Korolev wrote:
>>>> In pci_bios_map_regions() we try to reserve memory for
>>>>
On 03/01/12 22:48, Alexey Korolev wrote:
>> Hi,
>> What is your setup?
>> I want to reproduce this case
> qemu: latest master with a few patches (mst's bridge patches, pci64
> fixes from me, posted to qemu-devel a few days ago), bundle pushed to
> http://www.kraxe
> On Thu, Mar 01, 2012 at 06:50:43PM +1300, Alexey Korolev wrote:
>> Hi,
>>
>> This patch series enables 64bit BAR support in seabios.
>> It has a bit different approach for resources accounting, We did this
>> because we wanted:
>> a) Provide 64bit ba
On 05/03/12 23:12, Gerd Hoffmann wrote:
> Hi,
>
>> I can either send a patch over existing patches, or send new series or both.
> For testing a incremental patch is fine, for merge a new series with the
> fixes squashed into the buggy patches is needed.
>
> cheers,
> Gerd
Sure. Here are the hot
On 06/03/12 02:49, Kevin O'Connor wrote:
> On Mon, Mar 05, 2012 at 10:53:25AM +0100, Gerd Hoffmann wrote:
>>> Given the churn in this area, I don't want to commit patches that do
>>> wholesale code replacement. I'd prefer to see each patch
>>> independently add some functionality and perform its r
Hi,
This patch series redesigns the existing pciinit.c code and introduces
linked list operations.
Changes are more about structures definitions rather than functionality.
There are no more arrays of bases and counts in new implementation. The
new implementation is based on dynamic allocation of p
This linked list implementation is partially based on kernel code. So it
should be quite stable :)
Signed-off-by: Alexey Korolev
---
src/util.h | 32
1 files changed, 32 insertions(+), 0 deletions(-)
diff --git a/src/util.h b/src/util.h
index 70d3c4c
could keep code workable. I mean further patch
splitting is not possible as there are too many references to pci_bus
members.
Signed-off-by: Alexey Korolev
---
src/pci.h |6 --
src/pciinit.c | 266 ++---
2 files changed, 120 insertions
Now let simplify a bit a cumbersome code in pmm.c and stack.c
Signed-off-by: Alexey Korolev
---
src/pmm.c| 29 +
src/stacks.c |8 ++--
2 files changed, 11 insertions(+), 26 deletions(-)
diff --git a/src/pmm.c b/src/pmm.c
index c649fd8..996981c 100644
On 27/04/12 00:45, Kevin O'Connor wrote:
> On Wed, Apr 25, 2012 at 05:29:04PM +0200, Gerd Hoffmann wrote:
>> Issue #1: seabios can't boot from a virtio-scsi disk if the controller
>> is behind a pci bridge. I think the reason simply is that (according to
>> the seabios log) only root bus pci devi
Hi,
Tried these patches today on Win2008 x64 guest with 64bit devices.
I've got BSOD on boot. I guess windows don't like changes in _CRS.
On 04/05/12 20:21, Gerd Hoffmann wrote:
> Hi,
>
> This patch series makes the PCI I/O windows runtime-configurable via
> qemu firmware config interface. Main
1 - 100 of 114 matches
Mail list logo
