Default RAM backend depends on numa_uses_legacy_mem(), which is
infulenced by -numa options on CLI or set-numa-node QMP command
at preconfig time. If QEMU is started with '-preconfig'
without -numa, it will lead to creating default RAM backend
even if later set-numa-node is used to assing RAM to N
Options -M memory-backend and -numa memdev are mutually exclusive,
and if used together, it might lead to a crash in the worst case.
For example when the same backend is used with these options together:
-m 4G \
-object memory-backend-ram,id=mem0,size=4G \
-M pc,memory-backend=mem0 \
-numa
The options can't be used together (1st provides RAM for non-numa and fake-numa,
while 2nd provides RAM for each numa node).
If used together it might lead to crashes, so add a check to prevent
simultaneous
usage.
Igor Mammedov (2):
vl.c: run preconfig loop before creating default RAM backend
Cc'ing more developers.
On 5/11/20 4:17 PM, B3r3n wrote:
Dear all,
I am struggling for days/weeks with Qemu and its VNC accesses...with
non-US keymaps.
Let me summ the facts:
- I am using a french keyboard over a Ubuntu 18.04.
- I installed a simple Debian in a Qemu VM, configured with FR ke
On Mon, 11 May 2020 at 15:03, Peter Maydell wrote:
> Hmm. I get this link failure, but only on non-x86 hosts
> (aarch64, ppc, s390 [aarch32 ran into a temporary connectivity
> problem and didn't run]):
>
> linux-user/vm86.o: In function `do_int':
> /home/pm/qemu/linux-user/vm86.c:224: undefined re
On 5/9/20 1:08 AM, Collin Walling wrote:
> The SCCB must be checked for a sufficient length before it is filled
> with any data. If the length is insufficient, then the SCLP command
> is suppressed and the proper response code is set in the SCCB header.
>
> Signed-off-by: Collin Walling
Fixes ta
On Mon, May 04, 2020 at 10:49:11AM -0700, John G Johnson wrote:
>
>
> > On May 4, 2020, at 2:45 AM, Stefan Hajnoczi wrote:
> >
> > On Fri, May 01, 2020 at 04:28:25PM +0100, Daniel P. Berrangé wrote:
> >> On Fri, May 01, 2020 at 03:01:01PM +, Felipe Franciosi wrote:
> >>> Hi,
> >>>
> O
On 5/9/20 1:08 AM, Collin Walling wrote:
> It was never used in this function, so let's remove it.
>
> Signed-off-by: Collin Walling
Acked-by: Janosch Frank
> ---
> hw/s390x/sclp.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/hw/s390x/sclp.c b/hw/s390x/sclp.
Hi,
Have you decided whether to drop the remote device program in favor of
using a softmmu make target?
Is there anything in this series you'd like me to review before you send
the next revision?
Stefan
signature.asc
Description: PGP signature
On 11.05.20 16:36, Janosch Frank wrote:
> On 5/9/20 1:08 AM, Collin Walling wrote:
>> The SCCB must be checked for a sufficient length before it is filled
>> with any data. If the length is insufficient, then the SCLP command
>> is suppressed and the proper response code is set in the SCCB header.
On 5/11/20 10:44 AM, David Hildenbrand wrote:
On 11.05.20 16:36, Janosch Frank wrote:
On 5/9/20 1:08 AM, Collin Walling wrote:
The SCCB must be checked for a sufficient length before it is filled
with any data. If the length is insufficient, then the SCLP command
is suppressed and the proper re
Robert Foley writes:
> From: "Emilio G. Cota"
>
> This lock will soon protect more fields of the struct. Give
> it a more appropriate name.
Hmm while bisecting to find another problem I found this commit:
/home/alex/lsrc/qemu.git/hw/core/cpu.c: In function ‘cpu_common_finalize’:
/home/al
I have a similar problem with qemu (all versions including 5.0.0) on
MacOS-10.14.6 (mac book pro 2017with touch bar).
Using -k fr-mac the "@"/"#" key is dead.
Showkey doesn't detect the key.
Moreover, the # and @ symbols are mapped on the "<" / ">" key and thus I miss
the redirection operator in
Hello,
Jumping in the middle of this thread, so I apologize if some of my
comments are a bit out of context.
On Mon, May 11, 2020 at 11:06:34PM +0900, Keiichi Watanabe wrote:
> On Mon, May 11, 2020 at 9:33 PM Saket Sinha wrote:
> > > > > I do not support the approach of QEMU implementation forw
On 5/11/20 4:44 PM, David Hildenbrand wrote:
> On 11.05.20 16:36, Janosch Frank wrote:
>> On 5/9/20 1:08 AM, Collin Walling wrote:
>>> The SCCB must be checked for a sufficient length before it is filled
>>> with any data. If the length is insufficient, then the SCLP command
>>> is suppressed and t
i801_add_mux() fills in the GPIO lookup table by manually populating an
array of gpiod_lookup structures. Use the existing GPIO_LOOKUP() helper
macro instead, to relax a dependency on the gpiod_lookup structure's
member names.
Signed-off-by: Geert Uytterhoeven
Reviewed-by: Jean Delvare
---
This
GPIO controllers are exported to userspace using /dev/gpiochip*
character devices. Access control to these devices is provided by
standard UNIX file system permissions, on an all-or-nothing basis:
either a GPIO controller is accessible for a user, or it is not.
Currently no mechanism exists to con
Add a maintainership section for the GPIO Aggregator, covering
documentation and driver source code.
Signed-off-by: Geert Uytterhoeven
Reviewed-by: Eugeniu Rosca
Tested-by: Eugeniu Rosca
---
v7:
- Maintained => Supported,
v6:
- No changes,
v5:
- Add Reviewed-by, Tested-by,
v4:
- Drop
i801_add_mux() fills in the GPIO lookup table by manually populating an
array of gpiod_lookup structures. Use the existing GPIO_LOOKUP_IDX()
helper macro instead, to relax a dependency on the gpiod_lookup
structure's member names.
Signed-off-by: Geert Uytterhoeven
Acked-by: Lee Jones
---
v7:
Currently a GPIO lookup table can only refer to a specific GPIO by a
tuple, consisting of a GPIO controller label and a GPIO offset inside
the controller.
However, a GPIO may also carry a line name, defined by DT or ACPI.
If present, the line name is the most use-centric way to refer to a
GPIO. H
Document the GPIO Aggregator, and the two typical use-cases.
Signed-off-by: Geert Uytterhoeven
Reviewed-by: Ulrich Hecht
Reviewed-by: Eugeniu Rosca
Tested-by: Eugeniu Rosca
---
v7:
- No changes,
v6:
- Fix "allows" without object:
-> provides a mechanism to aggregate GPIOs,
->
Hi all,
GPIO controllers are exported to userspace using /dev/gpiochip*
character devices. Access control to these devices is provided by
standard UNIX file system permissions, on an all-or-nothing basis:
either a GPIO controller is accessible for a user, or it is not.
Currently no mechan
On Wed, Apr 29, 2020 at 03:53:58PM +1000, Geoffrey McRae wrote:
> This commit adds a new audiodev backend to allow QEMU to use JACK as
> both an audio sink and source.
>
> Signed-off-by: Geoffrey McRae
> ---
> audio/Makefile.objs| 5 +
> audio/audio.c | 1 +
> audio/audio_templa
On 2020-05-12 00:53, Stefan Hajnoczi wrote:
On Wed, Apr 29, 2020 at 03:53:58PM +1000, Geoffrey McRae wrote:
This commit adds a new audiodev backend to allow QEMU to use JACK as
both an audio sink and source.
Signed-off-by: Geoffrey McRae
---
audio/Makefile.objs| 5 +
audio/audio.c
On 11.05.20 16:50, Janosch Frank wrote:
> On 5/11/20 4:44 PM, David Hildenbrand wrote:
>> On 11.05.20 16:36, Janosch Frank wrote:
>>> On 5/9/20 1:08 AM, Collin Walling wrote:
The SCCB must be checked for a sufficient length before it is filled
with any data. If the length is insufficient,
On Mon, 11 May 2020 at 14:13, Patrick Williams wrote:
>
> On Mon, May 11, 2020 at 11:54:42AM +0100, Peter Maydell wrote:
> > On Wed, 6 May 2020 at 19:32, Patrick Williams wrote:
>
> > Looking up through the thread I can't find the email where
> > Amithash gave his reviewed-by tag -- did I miss it
On 11.05.20 15:58, Kevin Wolf wrote:
> This patch makes the raw image the same size as the file in a different
> format that is mirrored as raw to it to avoid errors when mirror starts
> to enforce that source and target are the same size.
>
> We check only that the first 512 bytes are zeroed (ins
On 5/11/20 2:51 AM, David Hildenbrand wrote:
> On 11.05.20 10:50, David Hildenbrand wrote:
> I'm having issues building this due to lack of HWCAP_S390_VX.
>
> [linux1@rhkvm01 qemu]$ cat /etc/redhat-release
> Red Hat Enterprise Linux Server release 7.7 (Maipo)
>
Yes, I found that when I pushed the
On Mon, May 11, 2020 at 04:24:32PM +0200, Philippe Mathieu-Daudé wrote:
> Cc'ing more developers.
>
> On 5/11/20 4:17 PM, B3r3n wrote:
> > Dear all,
> >
> > I am struggling for days/weeks with Qemu and its VNC accesses...with
> > non-US keymaps.
> >
> > Let me summ the facts:
> > - I am using a
Patchew URL:
https://patchew.org/QEMU/20200511133405.5275-1-peter.mayd...@linaro.org/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Message-id: 20200511133405.5275-1-peter.mayd...@linaro.org
Subject: [PULL 00/34] target-arm queue
Type: series
On 11.05.20 15:58, Kevin Wolf wrote:
> 229 relies on the mirror running into an I/O error when the target is
> smaller than the source. After changing mirror to catch this condition
> while starting the job, this test case won't get a job that is paused
> for an I/O error any more. Use blkdebug ins
On Thu 30 Apr 2020 01:10:17 PM CEST, Vladimir Sementsov-Ogievskiy wrote:
> The function is called from 64bit io handlers, and bytes is just passed
> to throttle_account() which is 64bit too (unsigned though). So, let's
> convert intermediate argument to 64bit too.
>
> This patch is a first in the 6
Am 11.05.2020 um 17:08 hat Max Reitz geschrieben:
> On 11.05.20 15:58, Kevin Wolf wrote:
> > This patch makes the raw image the same size as the file in a different
> > format that is mirrored as raw to it to avoid errors when mirror starts
> > to enforce that source and target are the same size.
>
On 200511 0910, Philippe Mathieu-Daudé wrote:
> On 5/11/20 8:19 AM, Philippe Mathieu-Daudé wrote:
> > On 5/11/20 6:59 AM, Alexander Bulekov wrote:
> > > Hello,
> > > While fuzzing, I found an input that triggers an assertion failure in
> > > mch_update_pciexbar:
> > >
> > > #6 0x7f38d387c55a in ab
On 11.05.20 15:58, Kevin Wolf wrote:
> If the target is shorter than the source, mirror would copy data until
> it reaches the end of the target and then fail with an I/O error when
> trying to write past the end.
>
> If the target is longer than the source, the mirror job would complete
> success
Am 11.05.2020 um 17:18 hat Max Reitz geschrieben:
> On 11.05.20 15:58, Kevin Wolf wrote:
> > 229 relies on the mirror running into an I/O error when the target is
> > smaller than the source. After changing mirror to catch this condition
> > while starting the job, this test case won't get a job th
On Thu 30 Apr 2020 01:10:18 PM CEST, Vladimir Sementsov-Ogievskiy wrote:
> We are generally moving to int64_t for both offset and bytes parameters
> on all io paths.
>
> Main motivation is realization of 64-bit write_zeroes operation for
> fast zeroing large disk chunks, up to the whole disk.
>
> W
I have been able to reproduce the issue and found that nodes are not
being removed from the AioContext->aio_handlers list when
aio_set_fd_handler() is called. perf shows that large amounts of CPU
time are spent in aio_pending().
Working on getting to the bottom of the issue and fixing it.
--
You
On 11.05.20 17:10, Richard Henderson wrote:
> On 5/11/20 2:51 AM, David Hildenbrand wrote:
>> On 11.05.20 10:50, David Hildenbrand wrote:
>> I'm having issues building this due to lack of HWCAP_S390_VX.
>>
>> [linux1@rhkvm01 qemu]$ cat /etc/redhat-release
>> Red Hat Enterprise Linux Server release
On 11.05.20 17:29, Kevin Wolf wrote:
> Am 11.05.2020 um 17:08 hat Max Reitz geschrieben:
>> On 11.05.20 15:58, Kevin Wolf wrote:
>>> This patch makes the raw image the same size as the file in a different
>>> format that is mirrored as raw to it to avoid errors when mirror starts
>>> to enforce tha
On 11.05.20 15:58, Kevin Wolf wrote:
> This tests that the mirror job catches situations where the target node
> has a different size than the source node. It must also forbid resize
> operations when the job is already running.
>
> Signed-off-by: Kevin Wolf
> Message-Id: <20200507145228.323412-4
ilable in the Git repository at:
>
> https://git.linaro.org/people/pmaydell/qemu-arm.git
> tags/pull-target-arm-20200511
>
> for you to fetch changes up to 7e17d50ebd359ee5fa3d65d7fdc0fe0336d60694:
>
> target/arm: Fix tcg_gen_gvec_du
* Daniel P. Berrangé (berra...@redhat.com) wrote:
> On Mon, May 11, 2020 at 01:07:18PM +0100, Dr. David Alan Gilbert wrote:
> > * Daniel P. Berrangé (berra...@redhat.com) wrote:
> > > On Mon, May 11, 2020 at 01:14:34PM +0200, Lukas Straub wrote:
> > > > Hello Everyone,
> > > > In many cases, if q
Attached to the mail counter.c when running with attached test.c compiled
to Linux standalone binary shows failing assert, unless the patch is
applied.
вс, 10 мая 2020 г. в 02:00, Emilio G. Cota :
> On Mon, Apr 20, 2020 at 13:04:51 +0300, Nikolay Igotti wrote:
> > In linux-user multithreaded scen
On Thu 30 Apr 2020 01:10:19 PM CEST, Vladimir Sementsov-Ogievskiy wrote:
> We are generally moving to int64_t for both offset and bytes parameters
> on all io paths.
>
> Main motivation is realization of 64-bit write_zeroes operation for
> fast zeroing large disk chunks, up to the whole disk.
>
> W
On Mon, 11 May 2020 15:23:37 +0530
Kirti Wankhede wrote:
> On 5/5/2020 10:07 AM, Alex Williamson wrote:
> > On Tue, 5 May 2020 04:48:14 +0530
> > Kirti Wankhede wrote:
> >
> >> On 3/26/2020 3:33 AM, Alex Williamson wrote:
> >>> On Wed, 25 Mar 2020 02:39:07 +0530
> >>> Kirti Wankhede wrote:
Hi Eduardo,
On 5/4/20 5:44 PM, Eduardo Habkost wrote:
On Thu, Apr 30, 2020 at 11:46:06AM -0400, Igor Mammedov wrote:
Since 5.0 QEMU uses hostmem backend for allocating main guest RAM.
The backend however calls mbind() which is typically NOP
in case of default policy/absent host-nodes bitmap.
Ho
Public bug reported:
Hello,
While fuzzing, I found an input that triggers an overlapping memcpy (caught by
AddressSanitizer).
Overlapping memcpys are undefined behavior according to the POSIX and C
standards, and can lead to bugs.
==22287==ERROR: AddressSanitizer: memcpy-param-overlap: memory r
On Mon, 11 May 2020 at 06:24, Alex Bennée wrote:
> Robert Foley writes:
snip
> > +/* XXX: is this really the max number of CPUs? */
> > +#define CPU_LOCK_BITMAP_SIZE 2048
>
> I wonder if we should be asserting this somewhere? Given it's an init
> time constant we can probably do it somewhere in t
This change will allow us to convert the bus children list to RCU,
while not changing the logic of this function
Signed-off-by: Maxim Levitsky
---
hw/scsi/scsi-bus.c | 12 ++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff --git a/hw/scsi/scsi-bus.c b/hw/scsi/scsi-bus.c
index 1c
Hi!
This is a patch series that is a result of my discussion with Paulo on
how to correctly fix the root cause of the BZ #1812399.
The root cause of this bug is the fact that IO thread is running mostly
unlocked versus main thread on which device hotplug is done.
qdev_device_add first creates th
Some code might race with placement of new devices on a bus.
We currently first place a (unrealized) device on the bus
and then realize it.
As a workaround, users that scan the child device list, can
check the realized property to see if it is safe to access such a device.
Use an atomic write here
This fixes the race between device emulation code that tries to find
a child device to dispatch the request to (e.g a scsi disk),
and hotplug of a new device to that bus.
Note that this doesn't convert all the readers of the list
but only these that might go over that list without BQL held.
This
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1812399
Suggested-by: Paolo Bonzini
Signed-off-by: Maxim Levitsky
---
hw/scsi/virtio-scsi.c | 19 ++-
1 file changed, 18 insertions(+), 1 deletion(-)
diff --git a/hw/scsi/virtio-scsi.c b/hw/scsi/virtio-scsi.c
index b0f4a35f8
This allows to preserve the semantics of hmp_device_del,
that the device is deleted immediatly which was changed by previos
patch that delayed this to RCU callback
Suggested-by: Stefan Hajnoczi
Signed-off-by: Maxim Levitsky
---
include/qemu/rcu.h | 1 +
qdev-monitor.c | 3 +++
util/rcu.c
This will help us to avoid the scsi device disappearing
after we took a reference to it.
It doesn't by itself forbid case when we try to access
an unrealized device
Suggested-by: Stefan Hajnoczi
Signed-off-by: Maxim Levitsky
---
hw/scsi/virtio-scsi.c | 23 +++
1 file change
Add scsi_device_get which finds the scsi device
and takes a reference to it.
Suggested-by: Stefan Hajnoczi
Signed-off-by: Maxim Levitsky
---
hw/scsi/scsi-bus.c | 31 ---
include/hw/scsi/scsi.h | 2 ++
2 files changed, 26 insertions(+), 7 deletions(-)
diff --git
On Mon, 11 May 2020 at 06:40, Alex Bennée wrote:
> Robert Foley writes:
>
> > From: "Emilio G. Cota"
> >
> > Cc: Palmer Dabbelt
> > Cc: Sagar Karandikar
> > Cc: Bastian Koppelmann
> > Cc: Alistair Francis
> > Reviewed-by: Palmer Dabbelt
>
> You can drop Cc: lines fron patches once you have
* Lukas Straub (lukasstra...@web.de) wrote:
> Add yank option, pass it to the socket-channel and register a yank
> function which sets s->state = NBD_CLIENT_QUIT. This is the same
> behaviour as if an error occured.
>
> Signed-off-by: Lukas Straub
> +static void nbd_yank(void *opaque)
> +{
> +
Public bug reported:
Hello,
While fuzzing, I found an input that triggers an overlapping memcpy (caught by
AddressSanitizer).
Overlapping memcpys are undefined behavior according to the POSIX and C
standards, and can lead to bugs.
==1==ERROR: AddressSanitizer: memcpy-param-overlap: memory r
On 4/30/20 12:21 AM, LIU Zhiwei wrote:
> It's some difficult when I try to support RV32, because it's very
> similiar to RV64, so I can't make two .risu files like arm.risu and
> aarch64.risu.
You could a command-line parameter, like --be or --sve for this.
r~
On Thu 30 Apr 2020 01:10:20 PM CEST, Vladimir Sementsov-Ogievskiy wrote:
> We are generally moving to int64_t for both offset and bytes parameters
> on all io paths.
>
> Main motivation is realization of 64-bit write_zeroes operation for
> fast zeroing large disk chunks, up to the whole disk.
>
> W
On Mon, 11 May 2020 at 10:48, Alex Bennée wrote:
> Hmm while bisecting to find another problem I found this commit:
>
> /home/alex/lsrc/qemu.git/hw/core/cpu.c: In function ‘cpu_common_finalize’:
> /home/alex/lsrc/qemu.git/hw/core/cpu.c:383:27: error: incompatible type for
> argument 1 of ‘qem
We made sure that iotests.py passes pylint. It would be a shame if we
allowed new patches in that break this again, so let's just add a
meta-test case that runs pylint on it.
While we don't pass mypy --strict yet, we can already run it with a few
options that would be part of --strict to make sure
We need to fix only a few places so that iotests.py can pass
mypy --disallow-incomplete-defs, which seems to be a desirable option to
have enabled in the long run.
Signed-off-by: Kevin Wolf
---
tests/qemu-iotests/iotests.py | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --gi
Kevin Wolf (2):
iotests: Fix incomplete type declarations
iotests: Run pylint and mypy in a testcase
tests/qemu-iotests/iotests.py | 8 +++
tests/qemu-iotests/297| 44 +++
tests/qemu-iotests/297.out| 3 +++
tests/qemu-iotests/group | 1 +
On 5/11/20 8:34 AM, David Hildenbrand wrote:
> Yes, compiles with that. Where are the arm sve tests located, so I can
> run them? (are they in tests/tcg?)
Ah, they're risu files. I'll find somewhere to share them.
r~
On 4/30/20 12:21 AM, LIU Zhiwei wrote:
> +LUI RISCV imm:20 rd:5 0110111 \
> +!constraints { $rd != 2 && $rd != 3 && $rd != 4 }
I think it would be helpful to add a function for this. e.g. greg($rd) and
gbase($rs1) (including $0). It would keep the constraints smaller, and avoid
mistakes.
These
We should add support of semtimedop syscall as new version of
glibc 2.31 uses semop based on semtimedop (commit:
https://gitlab.com/freedesktop-sdk/mirrors/sourceware/glibc/-/commit/765cdd0bffd77960ae852104fc4ea5edcdb8aed3
).
Signed-off-by: Matus Kysel
---
linux-user/syscall.c | 26 +++
On Sun, May 10, 2020 at 1:35 PM Philippe Mathieu-Daudé wrote:
>
> One can name a local variable holding a value as 'v', but it
> currently clashes with the registerfields macros. To save others
> to debug the same mistake, prefix the macro's local variables
> with an underscore.
>
> Signed-off-by:
On Mon, 11 May 2020 10:11:20 +0100
Peter Maydell wrote:
> On Sat, 9 May 2020 at 14:18, Lukas Straub wrote:
> > Hi,
> > Why not simply add slow tag to the test. Like:
> > :avocado: tags=slow
> >
> > The slow tests can then be skipped with
> > $ make check-acceptance AVOCADO_TAGS='-t -slow'
>
>
On Mon, 11 May 2020 11:44:26 +1000
David Gibson wrote:
> On Thu, May 07, 2020 at 07:26:32PM +0200, Greg Kurz wrote:
> > First three patches of this series are simple cleanups. The other
> > ones fix some regressions introduced by Cedric's recent addition
> > of partition-scoped translation.
>
>
Just because we're in a coroutine doesn't imply ownership of the context
of the flushed drive. In such a case use the slow path which explicitly
enters bdrv_flush_co_entry in the correct AioContext.
Signed-off-by: Stefan Reiter
---
We've experienced some lockups in this codepath when taking snap
On Mon, 11 May 2020 17:19:09 +0100
"Dr. David Alan Gilbert" wrote:
> * Lukas Straub (lukasstra...@web.de) wrote:
> > Add yank option, pass it to the socket-channel and register a yank
> > function which sets s->state = NBD_CLIENT_QUIT. This is the same
> > behaviour as if an error occured.
> >
>
Hi all,
This series adds dynamic GDB XML support for Micraoblaze CPUs, and fixes
an issue when reporting Microblaze SRegs through GDB.
The SRegs used to be printed out by iterating over the SReg array, but the
SReg array isn't laid out in memory in the same order that GDB expects them.
When repo
On Thu 30 Apr 2020 01:10:21 PM CEST, Vladimir Sementsov-Ogievskiy wrote:
> compute 'int tail' via % 'int alignment' - safe
tail = (offset + bytes) % alignment;
both are int64_t, no chance of overflow here?
Berto
On Mon, May 11, 2020 at 05:29:48PM +0200, B3r3n wrote:
> Hello Daniel,
>
> > There is no mention here of what VNC client program is being used, which
> > is quite important, as key handling is a big mess in VNC.
> I tested with TightVNC & noVNC through Apache. Both behaves the same. I did
> not te
SRegs used to be reported to GDB by iterating over the SRegs array,
however we do not store them in an order that allows them to be
reported to GDB in that way.
To fix this, a simple map is used to map the register GDB wants to its
location in the SRegs array.
Signed-off-by: Joe Komlodi
---
tar
Increase the number of registers reported to match GDB.
Registers that aren't modeled are reported as 0.
Signed-off-by: Joe Komlodi
---
target/microblaze/translate.c | 16 ++--
1 file changed, 14 insertions(+), 2 deletions(-)
diff --git a/target/microblaze/translate.c b/target/micr
Increase the number of Microblaze registers QEMU will report when
talking to GDB.
Signed-off-by: Joe Komlodi
---
target/microblaze/cpu.c | 2 +-
target/microblaze/gdbstub.c | 52 ++---
2 files changed, 50 insertions(+), 4 deletions(-)
diff --git a/ta
Add dynamic GDB register XML for Microblaze, and modify the config file to
use XML when building for Microblaze.
For the dynamic XML to be read, there still needs to be a core XML file.
Signed-off-by: Joe Komlodi
---
configure | 1 +
target/microblaze/cpu.c | 4 ++
targ
* Lukas Straub (lukasstra...@web.de) wrote:
> On Mon, 11 May 2020 17:19:09 +0100
> "Dr. David Alan Gilbert" wrote:
>
> > * Lukas Straub (lukasstra...@web.de) wrote:
> > > Add yank option, pass it to the socket-channel and register a yank
> > > function which sets s->state = NBD_CLIENT_QUIT. This
Forgot the attachment..
** Attachment added: "attachment"
https://bugs.launchpad.net/qemu/+bug/1878054/+attachment/5369967/+files/attachment
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1878054
Public bug reported:
Hello,
While fuzzing, I found an input that causes QEMU to hang with 100% CPU usage.
I have waited several minutes, and QEMU is still unresponsive. Using gdb, It
appears that it is stuck in an sdhci_data_transfer:
#0 memory_region_access_valid (mr=, addr=0x10284920,
size=,
On 4/30/20 12:21 AM, LIU Zhiwei wrote:
> +# sequence of li rd, 0x1234567887654321
> +#
> +# 0: 002471b7lui rd,0x247
> +# 4: 8ad1819baddiw rd,rd,-1875
> +# 8: 00c19193sllird,rd,0xc
> +# c: f1118193
Public bug reported:
Hello,
While fuzzing, I found an input that triggers a null-pointer dereference in
megasas_command_complete:
==14959==ERROR: AddressSanitizer: SEGV on unknown address 0x0003 (pc
0x55b1d11b4df1 bp 0x7ffeb55ca450 sp 0x7ffeb55ca1e0 T0)
==14959==The signal is caused by a
On 4/30/20 12:21 AM, LIU Zhiwei wrote:
> +struct reginfo {
> +uint64_t fault_address;
> +uint64_t regs[32];
> +uint64_t fregs[32];
> +uint64_t sp;
> +uint64_t pc;
> +uint32_t flags;
> +uint32_t faulting_insn;
> +
> +/* FP */
> +uint32_t fcsr;
> +};
There's no ne
The check to see if we can use FPU2 instructions would return 0 if
cfg.use_fpu == 2, rather than returning the PVR2_USE_FPU2_MASK.
This would cause all FPU2 instructions (fsqrt, flt, fint) to not be used.
Signed-off-by: Joe Komlodi
---
target/microblaze/translate.c | 2 +-
1 file changed, 1 ins
Hi all,
This fixes a backwards if statement that caused Microblaze FPU2 instructions
to not be executed, even if use-fpu=2 in the DTS.
Thanks!
Joe
Joe Komlodi (1):
target/microblaze: Fix FPU2 instruction check
target/microblaze/translate.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-
On 5/10/20 1:14 AM, xiaoqiang zhao wrote:
unix_listen/connect_saddr now support abstract address types
two aditional BOOL switches are introduced:
tight: whether to set @addrlen to the minimal string length,
or the maximum sun_path length. default is TRUE
abstract: whether we use abstrac
Patchew URL: https://patchew.org/QEMU/20200511160951.8733-1-mlevi...@redhat.com/
Hi,
This series failed the docker-quick@centos7 build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
=== TEST SCRIPT BEGIN ===
On 4/30/20 12:21 AM, LIU Zhiwei wrote:
> +void reginfo_init(struct reginfo *ri, ucontext_t *uc)
> +{
> +int i;
> +union __riscv_mc_fp_state *fp;
> +/* necessary to be able to compare with memcmp later */
> +memset(ri, 0, sizeof(*ri));
> +
> +for (i = 0; i < 32; i++) {
> +
On 4/30/20 12:21 AM, LIU Zhiwei wrote:
> Signed-off-by: LIU Zhiwei
> ---
> test_riscv64.s | 85 ++
> 1 file changed, 85 insertions(+)
> create mode 100644 test_riscv64.s
Reviewed-by: Richard Henderson
r~
Le 11/05/2020 à 13:12, Alex Bennée a écrit :
>
> Alex Bennée writes:
>
>> Hi,
>>
>> Cleaning up my queues into more focused trees these are all tweaks to
>> TCG related stuff. The guest_base changes where posted before but
>> where a little radical for 5.0 but I think are worth getting in early
Patchew URL: https://patchew.org/QEMU/20200511160951.8733-1-mlevi...@redhat.com/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Message-id: 20200511160951.8733-1-mlevi...@redhat.com
Subject: [PATCH v2 0/7] RFC/WIP: Fix scsi devices plug/unplug
On 4/30/20 12:21 AM, LIU Zhiwei wrote:
> +++ b/configure
> @@ -58,6 +58,8 @@ guess_arch() {
> ARCH="m68k"
> elif check_define __powerpc64__ ; then
> ARCH="ppc64"
> +elif check_define __riscv ; then
> +ARCH="riscv64"
> else
> echo "This cpu is not sup
On 5/11/20 11:03 AM, Richard Henderson wrote:
>> +if (m->regs[i] != a->regs[i]) {
>> +fprintf(f, " X%-2d: %016" PRIx64 " vs %016" PRIx64 "\n",
>> +i, m->regs[i], a->regs[i]);
>> +}
>
> riscv doesn't name its registers with an x.
Duh. It does.
Public bug reported:
Hello,
While fuzzing, I found an input that triggers an assertion failure in
eth_get_gso_type through the e1000e:
#1 0x7685755b in __GI_abort () at abort.c:79
#2 0x77c75dc3 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x77cd0b0a in g_asse
I've tested it (eventually, hit
https://github.com/torvalds/linux/commit/467d12f5c7842896d2de3ced74e4147ee29e97c8
while trying to build it),
it doesn't help, since my program wasn't failing from attempting to
use O_NOATIME.
The following patch fixed the -ENOENT on file create for me. I also
applie
On 4/30/20 12:21 AM, LIU Zhiwei wrote:
> +FCVT_L_S RISCV 110 00010 rs1:5 rm:3 rd:5 1010011 \
> +!constraints { $rd != 2 && $rd != 3 && $rd != 4 && $rm != 6 && $rm != 5 }
> +
> +FCVT_LU_S RISCV 110 00011 rs1:5 rm:3 rd:5 1010011 \
> +!constraints { $rd != 2 && $rd != 3 && $rd != 4 && $rm != 6
201 - 300 of 401 matches
Mail list logo
