On Monday 08 September 2014 02:17 AM, Alexander Graf wrote:
>
>
> On 25.08.14 15:45, Aravinda Prasad wrote:
>> This patch adds FWNMI support in qemu for powerKVM
>> guests by handling the ibm,nmi-register rtas call.
>> Whenever OS issues ibm,nmi-register RTAS call, the
>> machine check notifica
Am Sonntag, 5. Oktober 2014, 22:48:05 schrieb Peter Maydell:
> On 5 October 2014 22:36, Peter Maydell wrote:
> > On 5 October 2014 22:00, Michael Walle wrote:
> >> I can confirm that your patch makes qemu stop one instruction earlier.
> >> Without your patch the program is stopped at (3). With yo
On 5 October 2014 22:36, Peter Maydell wrote:
> On 5 October 2014 22:00, Michael Walle wrote:
>> I can confirm that your patch makes qemu stop one instruction earlier.
>> Without
>> your patch the program is stopped at (3). With your patch applied the program
>> is stopped at (2). But I guess th
On 5 October 2014 22:00, Michael Walle wrote:
> i've tested your patch on the lm32 target.
>
> My test program was like the following:
>
> mvhi r1, hi(0x1000)
> ori r1, r1, lo(0x1000)
> nop
> nop
> nop
> nop
> sw (r1+0), r0 ; (1) store some value to 0x1000
> nop; (2)
> nop
I have this problem (as describe in OP) on a Solaris 11.2 install using
the text iso. Archlinux Qemu 2.1.0. It appears that the above patch
has been applied to qemu for some time now (its also in my version).
Are there any new workarounds?
--
You received this bug notification because you are
Keys which send more than one scancode (esp. windows key) weren't handled
correctly since commit 1ff5eedd. Two events were put into the input event
queue but only one was processed. Fixes this by fetching all pending
events in the callback handler.
Signed-off-by: Michael Walle
Cc: Gerd Hoffmann
Am Freitag, 12. September 2014, 19:04:17 schrieb Peter Maydell:
> GDB assumes that watchpoint set via the gdbstub remote protocol will
> behave in the same way as hardware watchpoints for the target. In
> particular, whether the CPU stops with the PC before or after the insn
> which triggers the wa
Il 03/10/2014 23:33, Don Slutz ha scritto:
> From: "Dr. David Alan Gilbert"
>
> This is a pc & q35 only machine opt.
>
> VMWare apparently doesn't like running under QEMU due to our
> incomplete emulation of it's special IO Port. This adds a
> pc & q35 property to allow it to be turned off.
>
Il 05/10/2014 14:48, Michael S. Tsirkin ha scritto:
> In fact, if the pc_piix bits are dropped from the patch,
> you get a generic patchset that does exactly what you ask,
> correct?
>
> Downstream can then enable qemu-kvm compatibility by adding:
>
> -global cirrus-vga.vgamem_mb=16 -global pit-c
On Sun, Oct 05, 2014 at 08:26:45AM -0400, Paolo Bonzini wrote:
> > > > If you were just objecting to the fact that pc-1.0 was made to
> > > > be an alias of either one or the other at compile time, simply
> > > > drop the second patch of the v2 patchset.
> > >
> > > I was objecting to making pc-1.
> > > If you were just objecting to the fact that pc-1.0 was made to
> > > be an alias of either one or the other at compile time, simply
> > > drop the second patch of the v2 patchset.
> >
> > I was objecting to making pc-1.0 special. There's nothing special in
> > pc-1.0, other machine types al
Hi Valentin,
On Sun, Oct 5, 2014 at 7:06 PM, Valentin Manea wrote:
> Add support for the OpenCores keyboard device to the default OpenRisc
> machine.
>
> The OpenCores keyboard device is a simple open source keyboard device
> created by the OpenCores project(http://opencores.org/). By default it
Hi Valentin,
On Sun, Oct 5, 2014 at 7:07 PM, Valentin Manea wrote:
> The LPC32XX is a simple MMIO touch screen device with a Linux device
> driver. The device is suitable for small machines which require mouse
> input but have no suitable bus(SPI, I2C).
>
> Add the LPC32XX device to the default O
Hi Valentin,
On Sun, Oct 5, 2014 at 7:05 PM, Valentin Manea wrote:
> From edfd91e325a8c1806140c7468e187781d0b20ea9 Mon Sep 17 00:00:00 2001
> From: Valentin Manea
> Date: Sun, 21 Sep 2014 10:57:55 +0300
> Subject: [PATCH 2/4] target-openrisc: Add OpenCores FB device support
>
> Add support for t
Hi Valentin,
On Sun, Oct 5, 2014 at 7:03 PM, Valentin Manea wrote:
> Create new OpenRISC machine(asim) with default IDE support. It will
> incude more peripherals in order to run a fully fledged Linux computer.
>
> Signed-off-by: Valentin Manea
> ---
> default-configs/or32-softmmu.mak | 3 +
>
The LPC32XX is a simple MMIO touch screen device with a Linux device
driver. The device is suitable for small machines which require mouse
input but have no suitable bus(SPI, I2C).
Add the LPC32XX device to the default OpenRisc machine.
Signed-off-by: Valentin Manea
---
default-configs/or32-sof
Add support for the OpenCores keyboard device to the default OpenRisc
machine.
The OpenCores keyboard device is a simple open source keyboard device
created by the OpenCores project(http://opencores.org/). By default it
just forwards Linux like keycodes.
Signed-off-by: Valentin Manea
---
defaul
>From edfd91e325a8c1806140c7468e187781d0b20ea9 Mon Sep 17 00:00:00 2001
From: Valentin Manea
Date: Sun, 21 Sep 2014 10:57:55 +0300
Subject: [PATCH 2/4] target-openrisc: Add OpenCores FB device support
Add support for the OpenCores Framebuffer device and enable it by
default in the OpenRISC asim m
Create new OpenRISC machine(asim) with default IDE support. It will
incude more peripherals in order to run a fully fledged Linux computer.
Signed-off-by: Valentin Manea
---
default-configs/or32-softmmu.mak | 3 +
hw/openrisc/Makefile.objs| 1 +
hw/openrisc/openrisc_asim.c | 202
Hi,
After some extra feedback I made a new version of the openrisc
patches. However this time around I create a new "advanced" simulator
that includes all the new peripherals.
I would appreciate some feedback.
Thanks,
Valentin
On 5 Oct 2014, at 08:00, Paolo Bonzini wrote:
> Il 29/09/2014 09:02, Markus Armbruster ha scritto:
>>> If you were just objecting to the fact that pc-1.0 was made to
>>> be an alias of either one or the other at compile time, simply
>>> drop the second patch of the v2 patchset.
>
> I was object
Il 29/09/2014 09:02, Markus Armbruster ha scritto:
>> If you were just objecting to the fact that pc-1.0 was made to
>> be an alias of either one or the other at compile time, simply
>> drop the second patch of the v2 patchset.
I was objecting to making pc-1.0 special. There's nothing special in
22 matches
Mail list logo
