On Mon, Apr 20, 2015 at 04:32:12PM +0200, Michael S. Tsirkin wrote:
> On Mon, Apr 20, 2015 at 03:08:09PM +0100, Jan Beulich wrote:
> > >>> On 20.04.15 at 15:43, wrote:
> > > On Mon, Apr 13, 2015 at 01:51:06PM +0100, Jan Beulich wrote:
> > >> >>> On 13.04.15 at 14:47, wrote:
> > >> > Can you check
On 2015-06-06 12:10:03, Paulo Alcantara wrote:
> This patch initialises root complex register block BAR in order to
> support TCO watchdog emulation features (e.g. reboot upon NO_REBOOT bit
> not set) on QEMU.
>
> Contributed-under: TianoCore Contribution Agreement 1.0
> Signed-off-by: Paulo Alcan
Commit e2462113 allowed the ability to fire an event if a BDS
node exceeds a threshold during a write, but limited the option
to only work on node names. For convenience, expand this to
allow a device name as a way to set the threshold on the BDS
at the active layer of the device.
Signed-off-by:
On Mon, Jun 1, 2015 at 11:56 AM, Peter Maydell wrote:
> On 1 June 2015 at 19:04, Peter Crosthwaite
> wrote:
>> define the arm CP registers for PMSAv7 and their accessor functions.
>>
>> Signed-off-by: Peter Crosthwaite
>> ---
>> target-arm/cpu.h| 6 ++
>> target-arm/helper.c | 48
> On 07 Jun 2015, at 01:11, Peter Maydell wrote:
>
> ...
> So, there's two odd things here:
> (1) why ... a chunk ...
> (2) ... size in bytes ... flash_size_kb is what the name suggests, you're
> trying to map a region that's a lot smaller than you want.
right, this was a bug in my code.
t
On 6 June 2015 at 08:36, Sandhya Kumar wrote:
> Thanks Peter for your explanation.
>
> [The following question on TLB working could be a deviation from the first
> mail here, but asking here instead of starting new thread.]
>
> I picked up a simple 'Hello world' ELF executable (shown at the end) a
On 6 June 2015 at 20:01, Liviu Ionescu wrote:
> while working on the STM32 emulation, I noticed a problem related to the
> specific memory layout of STM32 devices.
>
> these devices have the FLASH region at 0x0800 instead of 0x, and
> since the specs require the presence of the reset
On Sat, Jun 6, 2015 at 11:11 AM, Liviu Ionescu wrote:
> in the [QOM Conventions](http://wiki.qemu.org/QOMConventions) page I noticed
>
> - DO use names-separated-by-dashes
>
> but looking at how objects are actually named I found a lot of names using
> underscores, dots, etc.
>
> did the
This patch initialises root complex register block BAR in order to
support TCO watchdog emulation features (e.g. reboot upon NO_REBOOT bit
not set) on QEMU.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Paulo Alcantara
---
OvmfPkg/Include/IndustryStandard/Q35MchIch9.h |
while working on the STM32 emulation, I noticed a problem related to the
specific memory layout of STM32 devices.
these devices have the FLASH region at 0x0800 instead of 0x, and
since the specs require the presence of the reset vector at 0x0, there is an
internal alias of the entir
Hi all.
Patch #1 is actually Pavel Fedin's patch
https://qemu-devel/2015-05/msg04495.html, which I included as a replacement
to my original patch #1 "as there could be only one". I think that Pavel's
needs to address all the issues in the original thread.
Best regards.
S.P.
On Jun 4, 2015 7:18 PM,
in the [QOM Conventions](http://wiki.qemu.org/QOMConventions) page I noticed
- DO use names-separated-by-dashes
but looking at how objects are actually named I found a lot of names using
underscores, dots, etc.
did the naming convention change, or was it simply ignored?
does the same
Public bug reported:
I am trying to run a guest mips32 program (user mode) on a x86_64 host. The
program fails on a call to shmat() reproducibly. when digging into this
problem, I could make a small guest POC that fails when compiled as i386 (-m32)
running on a x86_64 host, but pass when compi
On Jun 5, 2015 6:03 PM, Peter Maydell wrote:
>
> Ping?
I'll collect and review linux-user patches from the list on monday.
Riku
>
> thanks
> -- PMM
>
> On 26 May 2015 at 19:46, Peter Maydell wrote:
> > This patchset fixes some problems in conversions of cmsg structures
> > in target_to_ho
On 6 June 2015 at 02:37, Peter Crosthwaite wrote:
> On Fri, Jun 5, 2015 at 4:18 PM, Peter Maydell
> wrote:
>> Device reset is a sink and a quagmire. Note incidentally that what
>> we call "reset" in QEMU is actually "we hard powercycled the simulation",
>> not an emulated reset. If you can propo
On 6 June 2015 at 02:07, Peter Crosthwaite wrote:
> Should there be some sysbus_init_irq's?
Oops, yes...
(I don't have a test for this device specifically, so I haven't
been able to test beyond "does the zaurus image I have still boot?".)
-- PMM
On 6 June 2015 at 01:49, Peter Crosthwaite wrote:
> Ok that's all I found. So otherwise,
>
> Reviewed-by: Peter Crosthwaite
Thanks!
> I assume this is intended to break backwards compat on the VMSD with
> the conversion from put_byte loop to VMSTATE_UINT32_ARRAY? I'm not
> sure what our policy
> On 06 Jun 2015, at 01:54, Peter Maydell wrote:
>
> On 5 June 2015 at 22:11, Liviu Ionescu wrote:
>>
>>> On 05 Jun 2015, at 23:09, Leon Alrae wrote:
>>> ... how the
>>> TARGET_SYS_GET_CMDLINE should behave if cmdline is not available,
>>> whether should return -1 or pass an empty string to t
Thanks Peter for your explanation.
[The following question on TLB working could be a deviation from the first
mail here, but asking here instead of starting new thread.]
I picked up a simple 'Hello world' ELF executable (shown at the end) and
tried to experiment with QEMU's address translations (
19 matches
Mail list logo
