On Fri, Jan 22, 2010 at 8:51 PM, Artyom Tarasenko
wrote:
> 2010/1/22 Blue Swirl :
>> On Tue, Jan 19, 2010 at 9:44 PM, Artyom Tarasenko
>> wrote:
>>> 2010/1/19 Blue Swirl :
On Tue, Jan 19, 2010 at 5:30 PM, Artyom Tarasenko
wrote:
> 2010/1/15 Artyom Tarasenko :
>> 2010/1/15 Blue
Hi all,
when building git HEAD on an Ubuntu 9.10/64 with
--enable-debug, it breaks with
CCppc64-softmmu/translate.o
/home/jd/qemu/target-ppc/translate.c: In function ‘gen_mfdcr’:
/home/jd/qemu/target-ppc/translate.c:5568: error: incompatible type
for argument 1 of ‘gen_helper_load_dcr’
/hom
Hi all,
after reading the QEMU documentation and doing a search on the internet I
came to no clear statement whether QEMU's ARM emulation has also support
for the ARM security features known as TrustZone.
I found that QEMU emulates ARM Cortex-8 which in hardware have Trustzone
support. It is uncle
Hi,
I'm working on Qemu (0.9.0) extension in order to interact with SystemC (for
ARM system).
I would like to know where the ldl_code function is defined.
Qemu code use it on disas_arm_insn(...) function (code below):
static void disas_arm_insn(CPUState * env, DisasContext *s)
{
unsigned i
On Thu, Jan 21, 2010 at 5:27 PM, Bastien ROUCARIES
wrote:
> Hi,
>
> What is the step in order to get qemu android merged mainline ?
>
> http://android.git.kernel.org/?p=platform/external/qemu.git;a=summary
>
> Regards
>
> Bastien
>
BTW i am volonteer for the merge
Diff is 20M and I ask how can I
Hi there,
I have compiled qemu 0.12.2 on an x64 ubuntu (8.10) and run MusicPal
in it with SDL.
MusicPal works OK but there is no sound.
I have done essentially the same with qemu 0.11.1. The sound is there
(thanks jki for suggesting a previous version).
Please find below the configs and logs & c
Hi,
What is the step in order to get qemu android merged mainline ?
http://android.git.kernel.org/?p=platform/external/qemu.git;a=summary
Regards
Bastien
On 01/22/2010 01:03 PM, Adam Litke wrote:
Qemu has a number of commands that can operate asynchronously (savevm, migrate,
etc) and it will be getting more. For these commands, the user monitor needs
to be suspended, but QMP monitors could continue to to accept other commands.
This patch introduc
On 01/22/2010 02:09 PM, Luiz Capitulino wrote:
On Fri, 22 Jan 2010 12:05:19 -0600
Anthony Liguori wrote:
On 01/21/2010 03:09 PM, Luiz Capitulino wrote:
This commit disables asynchronous messages by default and
introduces two new QMP commands: async_msg_enable and
async_msg_disable.
fix a potential null pointer dereference introduced in
commit 576c2cdc767ab9e2dc038fa4c99f22e53287a3de
Signed-off-by: Artyom Tarasenko
---
diff --git a/target-sparc/op_helper.c b/target-sparc/op_helper.c
index ce8c6f1..eb4f5a4 100644
--- a/target-sparc/op_helper.c
+++ b/target-sparc/op_helper.c
Compilation of m68k-softmmu or m68k-linux-user on arm host
(or cross compilation for arm) results in a linker warning:
LINK m68k-softmmu/qemu-system-m68k
m68k-dis.o: warning: definition of `floatformat_ieee_single_little' overriding
common
arm-dis.o: warning: common is here
/usr/lib/gcc/arm-li
2010/1/22 Blue Swirl :
> On Tue, Jan 19, 2010 at 9:44 PM, Artyom Tarasenko
> wrote:
>> 2010/1/19 Blue Swirl :
>>> On Tue, Jan 19, 2010 at 5:30 PM, Artyom Tarasenko
>>> wrote:
2010/1/15 Artyom Tarasenko :
> 2010/1/15 Blue Swirl :
>> On Fri, Jan 15, 2010 at 9:11 PM, Artyom Tarasenko
>>
Toralf Förster wrote:
> Hi,
>
> under a mostly stable Gentoo I observed this new msg :
>
> tfoer...@n22 ~/virtual/kvm $ qemu -hda gentoo_kdevm.img -hdb
> portage_kdeprefix.img -hdd swap.img -smp 2 -m 768 -vga std -soundhw es1370
>
On Tue, Jan 19, 2010 at 10:25 PM, Igor V. Kovalenko
wrote:
> From: Igor V. Kovalenko
>
> sparc64 timer has tick counter which can be set and read,
> and tick compare value used as deadline to fire timer interrupt.
> The timer is not used as periodic timer, instead deadline
> is set each time new
On Fri, 22 Jan 2010 12:05:19 -0600
Anthony Liguori wrote:
> On 01/21/2010 03:09 PM, Luiz Capitulino wrote:
> > This commit disables asynchronous messages by default and
> > introduces two new QMP commands: async_msg_enable and
> > async_msg_disable.
> >
> > Each QMP Monitor has its own set of asy
Qemu has a number of commands that can operate asynchronously (savevm, migrate,
etc) and it will be getting more. For these commands, the user monitor needs
to be suspended, but QMP monitors could continue to to accept other commands.
This patch introduces a new command API that isolates the detai
On Fri, 22 Jan 2010, Markus Armbruster wrote:
> malc writes:
>
> > On Thu, 21 Jan 2010, Markus Armbruster wrote:
> >
> >> malc writes:
> >>
> >> > On Thu, 21 Jan 2010, Markus Armbruster wrote:
> >
> > [..snip..]
> >
> >> >> No, this is a misinterpretation of the C99 standard, made possible by
>
On Fri, 22 Jan 2010, Markus Armbruster wrote:
> malc writes:
>
> > On Thu, 21 Jan 2010, Jamie Lokier wrote:
> >
> >> Markus Armbruster wrote:
> >> > malc writes:
> >> >
> >> > > On Tue, 29 Dec 2009, Jamie Lokier wrote:
> >> > >
> >> > >> malc wrote:
> >> > >> > On Mon, 28 Dec 2009, Jamie Lokie
On 01/21/2010 03:09 PM, Luiz Capitulino wrote:
This commit disables asynchronous messages by default and
introduces two new QMP commands: async_msg_enable and
async_msg_disable.
Each QMP Monitor has its own set of asynchronous messages,
so for example, if QEMU is run with two QMP Monitors async
On 01/22/2010 07:47 AM, identifier scorpio wrote:
Is there any good method to find the bug except "guess and try"?
-singlestep -d in_asm,cpu,exec
Use these options on both Alpha host and x86_64 host and diff the
resulting output files. That will show you which target instruction is
emulated d
On Tue, Jan 19, 2010 at 9:44 PM, Artyom Tarasenko
wrote:
> 2010/1/19 Blue Swirl :
>> On Tue, Jan 19, 2010 at 5:30 PM, Artyom Tarasenko
>> wrote:
>>> 2010/1/15 Artyom Tarasenko :
2010/1/15 Blue Swirl :
> On Fri, Jan 15, 2010 at 9:11 PM, Artyom Tarasenko
> wrote:
>> 2010/1/15 Blue
On 01/21/2010 03:09 PM, Luiz Capitulino wrote:
"""
{"QMP": {"capabilities": ["async messages"]}}
{ "execute": "query-qmp-mode" }
{"return": {"mode": "handshake"}}
{ "execute": "change", "arguments": { "device": "vnc", "target": "password", "arg":
"1234" } }
{"error": {"class": "QMPInvalidModeC
I'll respin this series.
That's tough for us because on Windows, we store everything in a single
directory. That is, ${sysconfdir}/qemu wouldn't be a good base for us.
We would need to have sysconfdir and then a confdir that we could make
different for win32.
That makes sense. sysconf for system, conf for qemu.
Paol
On 01/22/2010 10:32 AM, Paolo Bonzini wrote:
On 01/22/2010 05:09 PM, Anthony Liguori wrote:
The default value is ${prefix}/etc/qemu. --sysconfdir can be used to
override
the default to an absolute path. The expectation is that when
installed to
/usr, --sysconfdir=/etc/qemu will be used.
So
On 01/22/2010 05:09 PM, Anthony Liguori wrote:
The default value is ${prefix}/etc/qemu. --sysconfdir can be used to override
the default to an absolute path. The expectation is that when installed to
/usr, --sysconfdir=/etc/qemu will be used.
Sorry for not being precise; --sysconfdir in Autoc
A new option, -nodefconfig is introduced to prevent loading from the default
config location. Otherwise, two configuration files will be searched for,
qemu.conf and target-.conf.
To ensure that the default configuration is overridden by a user specified
config, we introduce a two stage option par
This series introduces global config files stored in /etc/qemu. There is both
a common config (qemu.conf) and a per-target config (target-.conf).
I've removed the default device bits from the series as it requires some more
thought on how to best integrate it. That makes this series rather simpl
The default value is ${prefix}/etc/qemu. --sysconfdir can be used to override
the default to an absolute path. The expectation is that when installed to
/usr, --sysconfdir=/etc/qemu will be used.
Signed-off-by: Anthony Liguori
---
v1 -> v2
- rename to sysconf
---
configure | 10 ++
Signed-off-by: Anthony Liguori
---
vl.c | 72 +++--
1 files changed, 43 insertions(+), 29 deletions(-)
diff --git a/vl.c b/vl.c
index e070ec9..e00ae0d 100644
--- a/vl.c
+++ b/vl.c
@@ -4658,6 +4658,46 @@ static int debugcon_parse(const
Hi, Richard.
I almost re-write the whole code under your help and now it seems somehow
elegant. Unfortunately, it still can't run MS windows, I wonder whether there
are some other special places in QEMU to be modifed for alpha case, beside the
3 files (cpu-all.h/tcg-target.c/tcg-target.h) I wri
On 01/22/2010 04:15 AM, Markus Armbruster wrote:
Anthony Liguori writes:
This option can be used to toggle whether each default device is enabled or
disabled. For character devices, the default backend can also be overridden.
For devices, we'll have to take a different approach to changi
On 01/22/2010 05:00 AM, Gerd Hoffmann wrote:
On 01/21/10 19:48, Anthony Liguori wrote:
Introduce a default option to the network device which specifies that
this is
a default network device. This approach should generalize to any
other device.
The meaning of a default device is as follows: a
On 01/22/2010 06:43 AM, Paolo Bonzini wrote:
On 01/21/2010 07:48 PM, Anthony Liguori wrote:
--confdir can be used to override the
default to an absolute path. The expectation is that when installed
to /usr,
--confdir=/etc/qemu will be used.
Why not --sysconfdir? There are already several
Luiz Capitulino writes:
> On Fri, 22 Jan 2010 11:21:22 +0100
> Markus Armbruster wrote:
>
>> A few quick questions before I dive into the patches...
>>
>> Luiz Capitulino writes:
>>
>> > Feature negotiation allows clients to enable QMP capabilities they are
>> > interested in using. This all
This shouldn't happen under any normal circumstances. However, it looks like
it's possible to achieve this with corrupted images. Without this patch
raw_pread is hanging in an endless loop in such cases.
The patch is not affecting growable files, for which such reads happen in
normal use cases. ra
malc writes:
> On Thu, 21 Jan 2010, Jamie Lokier wrote:
>
>> Markus Armbruster wrote:
>> > malc writes:
>> >
>> > > On Tue, 29 Dec 2009, Jamie Lokier wrote:
>> > >
>> > >> malc wrote:
>> > >> > On Mon, 28 Dec 2009, Jamie Lokier wrote:
>> > >> >
>> > >> > > Aurelien Jarno wrote:
>> > >> > > > T
malc writes:
> On Thu, 21 Jan 2010, Markus Armbruster wrote:
>
>> malc writes:
>>
>> > On Thu, 21 Jan 2010, Markus Armbruster wrote:
>
> [..snip..]
>
>> >> No, this is a misinterpretation of the C99 standard, made possible by
>> >> its poor wording. The C99 Rationale is perfectly clear, though
On 01/21/2010 07:48 PM, Anthony Liguori wrote:
--confdir can be used to override the
default to an absolute path. The expectation is that when installed to /usr,
--confdir=/etc/qemu will be used.
Why not --sysconfdir? There are already several differences between
Autoconf options and QEMU
On Fri, 22 Jan 2010 11:21:22 +0100
Markus Armbruster wrote:
> A few quick questions before I dive into the patches...
>
> Luiz Capitulino writes:
>
> > Feature negotiation allows clients to enable QMP capabilities they are
> > interested in using. This allows QMP to envolve without breaking o
On Wed, Jan 20, 2010 at 6:43 PM, Stefan Weil wrote:
> Compilation for arm (native or cross) results in this
> warning:
>
> fpu/softfloat-native.c: In function ‘float64_round_to_int’:
> fpu/softfloat-native.c:387: error: control reaches end of non-void function
>
> float64_round_to_int uses special
Jamie Lokier writes:
> Markus Armbruster wrote:
>> I didn't claim there's *no* difference between C89 and C99. In fact,
>> the Rationale nicely documents the change:
>>
>> [snipped]
>> Also, implementations that support an
>> actual allocation when the size is zero do not necessaril
On 01/21/10 19:48, Anthony Liguori wrote:
Introduce a default option to the network device which specifies that this is
a default network device. This approach should generalize to any other device.
The meaning of a default device is as follows: a default device is added to a
machine IIF defa
On 01/21/10 19:48, Anthony Liguori wrote:
The ordering is a little troubling. Command line options are parsed before
loading the default configs which means that the command line configs will be
loaded before the default config. The effect is that the default config will
override -readconfig di
A few quick questions before I dive into the patches...
Luiz Capitulino writes:
> Feature negotiation allows clients to enable QMP capabilities they are
> interested in using. This allows QMP to envolve without breaking old clients.
>
> A capability is a new QMP feature and/or protocol change
Anthony Liguori writes:
> This option can be used to toggle whether each default device is enabled or
> disabled. For character devices, the default backend can also be overridden.
>
> For devices, we'll have to take a different approach to changing the defaults
> which will be covered in the ne
Luiz Capitulino writes:
> Hi,
>
> This new version fixes the printing of PCI bridge information,
> as I was able to test it after some help from Blue Swirl.
>
> Only the printing of PCI bridge attached devices remains
> untested, but according to Blue Swirl attaching devices to it
> is broken
47 matches
Mail list logo
