On Tue, Feb 7, 2017 at 1:03 PM, Alex Williamson
wrote:
> On Tue, 7 Feb 2017 12:53:04 -0500
> Jintack Lim wrote:
>
>> Thanks Alex, I appreciate your help.
>>
>> On Tue, Feb 7, 2017 at 12:09 PM, Alex Williamson
>>
On Tue, 7 Feb 2017 12:53:04 -0500
Jintack Lim wrote:
> Thanks Alex, I appreciate your help.
>
> On Tue, Feb 7, 2017 at 12:09 PM, Alex Williamson
> wrote:
> > On Tue, 7 Feb 2017 11:46:57 -0500
> > Jintack Lim wrote:
Thanks Alex, I appreciate your help.
On Tue, Feb 7, 2017 at 12:09 PM, Alex Williamson
wrote:
> On Tue, 7 Feb 2017 11:46:57 -0500
> Jintack Lim wrote:
>
>> Adding CC and some more information.
>
> $ ./scripts/get_maintainer.pl -f
On 5 February 2017 at 14:27, Hrishikesh Murukkathampoondi
wrote:
> * a flash device at 0x0
> * RAM starting at 0x4000
You can also get away with hardcoding the UART being at
0x0900 (since UEFI hardcodes that too).
> He mentioned that all other values like -machine
On Tue, 7 Feb 2017 11:46:57 -0500
Jintack Lim wrote:
> Adding CC and some more information.
$ ./scripts/get_maintainer.pl -f ./hw/i386/intel_iommu.c
get_maintainer.pl: No maintainers found, printing recent contributors.
get_maintainer.pl: Do not blindly cc: them on
On 7 February 2017 at 15:26, Thomas Huth wrote:
> On 07.02.2017 11:06, James Hanley wrote:
>> Why the new domain?
>
> It's not new, it's the official domain of the QEMU project.
Yes, we've always had both domains in parallel. The recent
change is that qemu.org now redirects to
>Alle domenica 15 gennaio 2017, hai scritto:
I try with debian-7.11.0-sparc-DVD-1.iso (as the suggested guide)
qemu-system-sparc64 -L pc-bios -m
384 -nographic -kernel /.../sparc64 -initrd /.../initrd+virtio.gz -drive
file=/.../sparc64.img,if=virtio,index=0 -drive
On 07.02.2017 11:06, James Hanley wrote:
> Why the new domain?
It's not new, it's the official domain of the QEMU project.
For some historical details see:
http://git.qemu-project.org/?p=qemu.git;a=commitdiff;h=859389810910
(though the situation has improved nowadays, as far as I know)
Thomas
When doing full system emulation, QEMU provides us with an option to trace
events which can then be analysed(for eg. the simple trace backend). I
wanted to know if it's possible for me to trace the execution
flow(tb_exec,translate_block etc) when using the user mode emulation to run
a 32 bits MIPS
Why the new domain?
-Jim
> On Feb 7, 2017, at 1:38 AM, Vincenzo Romano
> wrote:
>
> When going to the qemu.org with your brwoser, you'll be redirected to
> the new website qemu-project.org!
>
> You're all invited! Bring your (virtual) glass to toast it!
>
> --
>
10 matches
Mail list logo