Dear Philippe, thank you for your kind response.
I will send a new version for the patch with the modifications you've
highlighted, but first I've some question on the best way to implement
them.
On Tue, Feb 09, 2021 at 12:30:32PM +0100, Philippe Mathieu-Daudé wrote:
Hi Davide,
On 2/
The bcm2835 GPIOs now generate interrupts.
This modification enables QTEST clients to trigger interrupt-based
interfaces.
Signed-off-by: Davide Berardi
---
hw/arm/bcm2835_peripherals.c | 2 +
hw/gpio/bcm2835_gpio.c | 105 +
hw/intc/bcm2835_ic.c
The bcm2835 GPIOs now generate interrupts.
This modification enables QTEST clients to trigger interrupt-based
interfaces.
Signed-off-by: Davide Berardi
---
hw/arm/bcm2835_peripherals.c | 2 +
hw/gpio/bcm2835_gpio.c | 105 +
hw/intc/bcm2835_ic.c
any solution? trying to emulate a closed source amd64 app on my
raspberry and i'm getting this error with qemu 5.2.0-rc4 and glibc 2.27.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1673976
Title:
Right now with
`qemu-system-arm -kernel kernel7.img -dtb bcm2709-rpi-2-b.dtb -cpu arm1176 -M
raspi2 -hda 2018-11-13-raspbian-stretch-full.img`
I can access the serial console using `Ctrl+Alt+3` in the QEMU window.
Using raspbian via this serial console is (as far as I can see) the same as
using
Public bug reported:
** Setup: **
→ Host
Qemu version 2.4.0.1
Linux: 4.1.1 (Debian 8.2, GCC 4.9.2, x86_64)
filesystem ext3 and ext4
one single host machine
→ Guests (3 VMs)
architecture x86_64, Linux 3.16.0-4-amd64 (Debian 7.6)
virtual disk qcow2, uncompressed
guests
Where I can find i386 flags after every instruction??
I run qemu in single step mode and user-mode. I want to know where i386
flags are stored after a run of one Translation Block.
I run qemu in single step mode and user-mode. I want to know where i386
flags are stored after a run of one Translation Block.
Yes this is definitely an option :)
Just for curiosity, what is the effect of "in-kernel irqchip"?
Is it possible to disable it on a "live" domain?
Cheers,
Davide
On 14/mar/2013, at 19:21, Peter Lieven wrote:
>
> Am 14.03.2013 um 19:15 schrieb Davide Guerri :
>
s have reported
>> again this bug with guest kernel 2.6.32. (proxmox host is rhel 6.3 kernel +
>> qemu 1.4)
>>
>>
>>
>> - Mail original -
>>
>> De: "Davide Guerri"
>> À: "Alexandre DERUMIER"
>> Cc:
gh: that machine was almost
unusable!
Does version 1.3 fixes this issue?
Could someone with the required knowledge look into this, please?
Please, this is a very nasty bug because I guess I'm not the only one who is
unable to upgrade all the machines with a (not-so) old kernel... :)
Thanks!
Those is my post.
This problem is only my. I don't find these library. I don't know where
to download them.
On 06/28/12 10:22, Dunrong Huang wrote:
This post may give you some advice
http://lists.gnu.org/archive/html/qemu-devel/2012-06/msg02319.html
2012/6/28 Davide Ferraretto
I want compile qemu with --static:
./configure --static --target-list=i386-linux-user,arm-linux-user
--python=/usr/bin/python2.7 --prefix=/install_qemu
Qemu returns:
/usr/bin/ld: cannot find -lssl3
/usr/bin/ld: cannot find -lsmime3
/usr/bin/ld: cannot find -lnss3
/usr/bin/ld: cannot find -lnssuti
I want compile qemu with --static: ./configure --static
--target-list=i386-linux-user,arm-linux-user --python=/usr/bin/python2.7
--prefix=/install_qemu
Qemu returns: /usr/bin/ld: cannot find -lssl3 /usr/bin/ld: cannot find
-lsmime3 /usr/bin/ld: cannot find -lnss3 /usr/bin/ld: cannot find
-ln
I want compile qemu with --static:
./configure --static --target-list=i386-linux-user,arm-linux-user
--python=/usr/bin/python2.7 --prefix=/install_qemu
Qemu returns:
/usr/bin/ld: cannot find -lssl3
/usr/bin/ld: cannot find -lsmime3
/usr/bin/ld: cannot find -lnss3
/usr/bin/ld: cannot find -lnssu
I'm in qemu-arm.
tcg_qemu_tb_exec function is a macro:
#define tcg_qemu_tb_exec(env, tb_ptr)\
((long REGPARM (*)(void *, void *))code_gen_prologue)(env, tb_ptr)
#endif
I don't understand what function calls. where is code of
code_gen_prologue???
I'm in "arm user space" with "sigle step mode". I want write "exit\n" in
linux shell (no QEMU monitor) when emulate code arrives to "return 0"
On 06/01/12 14:23, Max Filippov wrote:
On Fri, Jun 1, 2012 at 3:57 PM, Davide Ferraretto
wrote:
I tr
I tried to insert " printf("exit\n"); ", but qemu dosen't write to monitor.
On 06/01/12 13:43, Max Filippov wrote:
On Fri, Jun 1, 2012 at 3:16 PM, Davide Ferraretto
wrote:
In arm user mode, where does qemu exit? Where is last qemu's instruction?
I.E.
int main (
In arm user mode, where does qemu exit? Where is last qemu's instruction?
I.E.
int main (){return 0;}
in what file does qemu run "return 0"??
In arm user mode, where does qemu exit? Where is last qemu's instruction?
Hi!!!
1)How can I use cpsr_write(var, tmp_mask) in qemu- arm(user mode)??
2)What are "var" and "tmp_mask"??
3)How does QEMU use cpsr register in "sigle step mode"??
But, I work into qemu code. Is there a c qemu function for this??
On 05/07/12 19:10, Mulyadi Santosa wrote:
On Mon, May 7, 2012 at 11:49 PM, Davide Ferraretto
wrote:
how can I read location of memory poits by esp register (i386 cpu)??
CMIIW, using gdb stub hooked to Qemu, it should be:
p
how can I read location of memory poits by esp register (i386 cpu)??
In qemu-i386 can I know "How many bytes is a instruction before it run"??
In qemu where is "Instruction Register"??
In qemu in i386, where are cc and df flags??
What does "ldub_code(s->pc++);" do???
In target-i386/translate.c there are this instructions:
int op, f, val;
op = (b >> 3) & 7;
f = (b >> 1) & 3;
if ((b & 1) == 0)
ot = OT_BYTE;
else
ot = dflag + OT_WORD;
What does this code do??
Where is that qemu read instructions of source file??
What does "target_pread" function do in flatload.c???
What does this loop in main?
for (wrk = environ; *wrk != NULL; wrk++) {
(void) envlist_setenv(envlist, *wrk);
}
What does this loop in main?
for (wrk = environ; *wrk != NULL; wrk++) {
(void) envlist_setenv(envlist, *wrk);
}
It dosen't work. GDB returns the same error.
- Original Message -
From: davide.ferrare...@studenti.univr.it
Date: Monday, October 24, 2011 8:37
Subject: Re: [Qemu-discuss] [Qemu-discussion] QEMU via GDB
To: davide.ferrare...@studenti.univr.it
> It dosen't work. GDB return the same error.
Dear all,
I am trying to debug QEMU via GDB.
I configured and compiled QEMU with debugging flags, i.e.,
# CFLAGS="-g3 -O0" ./configure --disable-gfx-check
and run gdb:
# gdb ./i386-linux-user/qemu-i386
(gdb) break main
(gdb) run
Starting program: /home/test/femu/i386-linux
Dear all,
I am trying to debug QEMU via GDB.
I configured and compiled QEMU with debugging flags, i.e.,
# CFLAGS="-g3 -O0" ./configure --disable-gfx-check
and run gdb:
# gdb ./i386-linux-user/qemu-i386
(gdb) break main
(gdb) run
Starting program: /home/test/femu/i386-linux-user/qemu-i386
36 matches
Mail list logo
