Il 16/07/2013 18:59, Hervé Poussineau ha scritto:
> Paolo Bonzini a écrit :
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Il 16/07/2013 09:18, Jan Kiszka ha scritto:
>>> Sorry for sending out invitations and then being late to this party
>>> - vacation. What is the status now? Do we hav
Paolo Bonzini a écrit :
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 16/07/2013 09:18, Jan Kiszka ha scritto:
Sorry for sending out invitations and then being late to this party
- vacation. What is the status now? Do we have a short-term plan to
avoid the regression or is this better solved
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 16/07/2013 09:18, Jan Kiszka ha scritto:
> Sorry for sending out invitations and then being late to this party
> - vacation. What is the status now? Do we have a short-term plan to
> avoid the regression or is this better solved by cleaning up the
>
On 2013-07-14 17:18, Anthony Liguori wrote:
> On Sun, Jul 14, 2013 at 9:58 AM, Peter Maydell
> wrote:
>> On 14 July 2013 14:05, Anthony Liguori wrote:
Also, what devices exactly would have a non-native byte order?!? I'm
confused...
>>>
>>> MMIO/PIO requests don't have a byte order. I
On 14 July 2013 16:18, Anthony Liguori wrote:
> On Sun, Jul 14, 2013 at 9:58 AM, Peter Maydell
> wrote:
>> Devices themselves do have a byte order, though, right? Specifically,
>> if you do a 32 bit read of address 0 on a device and an 8 bit read,
>
> It depends on the bus and device. Busses do
On Sun, Jul 14, 2013 at 9:58 AM, Peter Maydell wrote:
> On 14 July 2013 14:05, Anthony Liguori wrote:
>>> Also, what devices exactly would have a non-native byte order?!? I'm
>>> confused...
>>
>> MMIO/PIO requests don't have a byte order. It's literally 64 or 32 data
>> pins that are numbered
On 14 July 2013 14:05, Anthony Liguori wrote:
>> Also, what devices exactly would have a non-native byte order?!? I'm
>> confused...
>
> MMIO/PIO requests don't have a byte order. It's literally 64 or 32 data
> pins that are numbered D0..D31 whereas D0 is the LSB. It doesn't matter
> how the pi
Paolo Bonzini writes:
> Il 13/07/2013 17:22, Anthony Liguori ha scritto:
>> 1) MMIO request goes to sPAPR PIO area, the vCPU was in BE mode but by
>> the time the handler is called, the value is in host byte order.
>>
>> 2) sPAPR (incorrectly) byte swaps by marking the region as little
>> endian
Il 13/07/2013 17:22, Anthony Liguori ha scritto:
> 1) MMIO request goes to sPAPR PIO area, the vCPU was in BE mode but by
> the time the handler is called, the value is in host byte order.
>
> 2) sPAPR (incorrectly) byte swaps by marking the region as little
> endian (data is now garbage)
>
> 3)
Anthony Liguori a écrit :
On Sat, Jul 13, 2013 at 9:38 AM, Paolo Bonzini wrote:
Il 11/07/2013 14:46, Andreas Färber ha scritto:
sPAPR has its MemoryRegion marked Little Endian:
http://git.qemu.org/?p=qemu.git;a=blobdiff;f=hw/spapr_pci.c;h=a08ed11166595bdc493065beb64d4ce5b7b0dded;hp=c2c3079d21
On Sat, Jul 13, 2013 at 9:38 AM, Paolo Bonzini wrote:
> Il 11/07/2013 14:46, Andreas Färber ha scritto:
>> sPAPR has its MemoryRegion marked Little Endian:
>>
>> http://git.qemu.org/?p=qemu.git;a=blobdiff;f=hw/spapr_pci.c;h=a08ed11166595bdc493065beb64d4ce5b7b0dded;hp=c2c3079d21d5be2647faf85a8c608a
Il 11/07/2013 14:46, Andreas Färber ha scritto:
> sPAPR has its MemoryRegion marked Little Endian:
>
> http://git.qemu.org/?p=qemu.git;a=blobdiff;f=hw/spapr_pci.c;h=a08ed11166595bdc493065beb64d4ce5b7b0dded;hp=c2c3079d21d5be2647faf85a8c608ac995d2ca62;hb=a3cfa18eb075c7ef78358ca1956fe7b01caa1724;hpb=
Hervé Poussineau writes:
> Jan Kiszka a écrit :
>> From: Jan Kiszka
>>
>> The current ioport dispatcher is a complex beast, mostly due to the
>> need to deal with old portio interface users. But we can overcome it
>> without converting all portio users by embedding the required base
>> address
Am 12.07.2013 um 14:56 schrieb Anthony Liguori :
> Alexander Graf writes:
>
>> On 11.07.2013, at 14:29, Alexander Graf wrote:
>>
>>> This patch breaks VGA on PPC as it is in master today.
>>
>> If I don't mark portio as little endian it works as expected. There's
>> probably someone swapping
Alexander Graf writes:
> On 11.07.2013, at 14:29, Alexander Graf wrote:
>
>> This patch breaks VGA on PPC as it is in master today.
>
> If I don't mark portio as little endian it works as expected. There's
> probably someone swapping things twice.
This is the correct fix. Can you please send a
On 11.07.2013, at 15:28, Alexander Graf wrote:
>
> On 11.07.2013, at 14:48, Alexander Graf wrote:
>
>>
>> On 11.07.2013, at 14:46, Andreas Färber wrote:
>>
>>> Am 11.07.2013 14:34, schrieb Alexander Graf:
On 11.07.2013, at 14:29, Alexander Graf wrote:
>
> On 24.06.20
On 11.07.2013, at 14:48, Alexander Graf wrote:
>
> On 11.07.2013, at 14:46, Andreas Färber wrote:
>
>> Am 11.07.2013 14:34, schrieb Alexander Graf:
>>>
>>> On 11.07.2013, at 14:29, Alexander Graf wrote:
>>>
On 24.06.2013, at 08:07, Jan Kiszka wrote:
> On 2013-06-23 22:50,
On 11.07.2013, at 14:46, Andreas Färber wrote:
> Am 11.07.2013 14:34, schrieb Alexander Graf:
>>
>> On 11.07.2013, at 14:29, Alexander Graf wrote:
>>
>>>
>>> On 24.06.2013, at 08:07, Jan Kiszka wrote:
>>>
On 2013-06-23 22:50, Hervé Poussineau wrote:
> Jan Kiszka a écrit :
>> From
Am 11.07.2013 14:34, schrieb Alexander Graf:
>
> On 11.07.2013, at 14:29, Alexander Graf wrote:
>
>>
>> On 24.06.2013, at 08:07, Jan Kiszka wrote:
>>
>>> On 2013-06-23 22:50, Hervé Poussineau wrote:
Jan Kiszka a écrit :
> From: Jan Kiszka
>
> The current ioport dispatcher is a c
On 11.07.2013, at 14:29, Alexander Graf wrote:
>
> On 24.06.2013, at 08:07, Jan Kiszka wrote:
>
>> On 2013-06-23 22:50, Hervé Poussineau wrote:
>>> Jan Kiszka a écrit :
From: Jan Kiszka
The current ioport dispatcher is a complex beast, mostly due to the
need to deal with o
On 24.06.2013, at 08:07, Jan Kiszka wrote:
> On 2013-06-23 22:50, Hervé Poussineau wrote:
>> Jan Kiszka a écrit :
>>> From: Jan Kiszka
>>>
>>> The current ioport dispatcher is a complex beast, mostly due to the
>>> need to deal with old portio interface users. But we can overcome it
>>> without
On 2013-06-23 22:50, Hervé Poussineau wrote:
> Jan Kiszka a écrit :
>> From: Jan Kiszka
>>
>> The current ioport dispatcher is a complex beast, mostly due to the
>> need to deal with old portio interface users. But we can overcome it
>> without converting all portio users by embedding the required
Jan Kiszka a écrit :
From: Jan Kiszka
The current ioport dispatcher is a complex beast, mostly due to the
need to deal with old portio interface users. But we can overcome it
without converting all portio users by embedding the required base
address of a MemoryRegionPortio access into that data
From: Jan Kiszka
The current ioport dispatcher is a complex beast, mostly due to the
need to deal with old portio interface users. But we can overcome it
without converting all portio users by embedding the required base
address of a MemoryRegionPortio access into that data structure. That
remove
24 matches
Mail list logo
