On Fri, Jul 31, 2015 at 03:08:09PM +0300, Vasiliy Tolstov wrote:
> 2015-07-31 14:55 GMT+03:00 Vasiliy Tolstov :
> > Liu's patch also works for me. But also like in Hitoshi patch breaks
> > when using discards in qemu =(.
>
>
> Please wait to performance comparison. As i see Liu's patch may be
> m
On 01/08/15 19:33, Aurelien Jarno wrote:
> On 2015-08-01 17:54, Mark Cave-Ayland wrote:
>> The existing code incorrectly changes the dma_active flag when a non-block
>> transfer has completed leading to a hang on newer versions of Linux because
>> the
>> IDE and DMA engines deadlock waiting for e
On 2015-08-01 17:54, Mark Cave-Ayland wrote:
> The existing code incorrectly changes the dma_active flag when a non-block
> transfer has completed leading to a hang on newer versions of Linux because
> the
> IDE and DMA engines deadlock waiting for each other.
>
> Instead copy the buffer directly
The existing code incorrectly changes the dma_active flag when a non-block
transfer has completed leading to a hang on newer versions of Linux because the
IDE and DMA engines deadlock waiting for each other.
Instead copy the buffer directly to RAM, set the remaining transfer size to 0
and
then in
Le 01/08/2015 09:57, Markus Armbruster a écrit :
Jean-Christophe Dubois writes:
The "chardev" property initialization might have failed (for example because
there are not enough chardevs provided by QEMU).
The serial device emulator need to be able to work with an uninitialized
(NULL) chardev
The existing code incorrectly changes the dma_active flag when a non-block
transfer has completed leading to a hang on newer versions of Linux because the
IDE and DMA engines deadlock waiting for each other.
Instead copy the buffer directly to RAM, set the remaining transfer size to 0
and
then in
On 01/08/15 13:37, Aurelien Jarno wrote:
> On 2015-08-01 12:21, Mark Cave-Ayland wrote:
>> On 28/07/15 19:02, Aurelien Jarno wrote:
>>
Thanks for the heads-up. I have a fairly comprehensive suite of various
OS test images I use for OpenBIOS testing and evidently not a single one
of
Public bug reported:
In the arm_timer.c, when first reading the load register, I got 0.
...
case 0: /* TimerLoad */
...
According to the specification at
http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0271d/index.html,
"The minimum valid value for TimerXLoad is 1". Is the in
Yes. In our pl050 keyboard controller, the KMIDATA is reset once the
receive queue is empty.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1478376
Title:
PL050 KMIDATA register does not reset
Stat
On 2015-08-01 12:21, Mark Cave-Ayland wrote:
> On 28/07/15 19:02, Aurelien Jarno wrote:
>
> >> Thanks for the heads-up. I have a fairly comprehensive suite of various
> >> OS test images I use for OpenBIOS testing and evidently not a single one
> >> of them issues a TRIM command as I don't see any
On 2015-08-01 12:10, Mark Cave-Ayland wrote:
> On 29/07/15 20:27, Aurelien Jarno wrote:
>
> > Commit bd4214fc dropped TRIM support by mistake. Given it is still
> > advertised to the host when using a drive with discard=on, this cause
> > the IDE bus to hang when the host issues a TRIM command.
>
On 28/07/15 19:02, Aurelien Jarno wrote:
>> Thanks for the heads-up. I have a fairly comprehensive suite of various
>> OS test images I use for OpenBIOS testing and evidently not a single one
>> of them issues a TRIM command as I don't see any regressions here. Can
>> you point me towards the part
On 29/07/15 20:27, Aurelien Jarno wrote:
> Commit bd4214fc dropped TRIM support by mistake. Given it is still
> advertised to the host when using a drive with discard=on, this cause
> the IDE bus to hang when the host issues a TRIM command.
>
> This patch fixes that by re-adding the TRIM code, po
Hello All:
I am just adding floating point instructions (e.g. fsingle_add1), but
for me, I can not find any details about them (the ISA documents only
give a summary description, but not details), e.g.
fsingle_add1
Floating Point Single Precision Add Part 1
Syntax
fsingle_add1 De
On 31/07/2015 20:11, Jason J. Herne wrote:
>>>
>>
>> Doh! Yep :). This problem is an artifact of moving the timer_mod from
>> cpu_throttle_thread into cpu_throttle_timer_tick. I'll have to go back
>> to the review comments and look at why that was done.
>
> So, we made that change in v3 to elimi
Jean-Christophe Dubois writes:
> The "chardev" property initialization might have failed (for example because
> there are not enough chardevs provided by QEMU).
>
> The serial device emulator need to be able to work with an uninitialized
> (NULL) chardev device pointer.
>
> This patch add some mi
16 matches
Mail list logo
