On Wed, 25 Aug 2021, Mark Cave-Ayland wrote:
> On 24/08/2021 11:09, Finn Thain wrote:
>
> > This is a patch series that I started last year. The aim was to try to
> > get a monotonic clocksource for Linux/m68k guests. That aim hasn't been
> > achieved yet (for q800 machines) but I'm submitting
On 8/26/21 6:54 AM, Peter Maydell wrote:
On Sat, 21 Aug 2021 at 21:09, Richard Henderson
wrote:
+/*
+ * From v8, it is CONSTRAINED UNPREDICTABLE whether BXWritePC aligns
+ * the address or not. If so, we can legitimately fall through.
+ */
+return EXIT_SUCCESS;
+}
Can
On Tue, 24 Aug 2021, Philippe Mathieu-Daudé wrote:
> On 8/24/21 12:09 PM, Finn Thain wrote:
>
> > On a real Quadra, accesses to the SY6522 chips are slow because they are
> > synchronous with the 783360 Hz "phase 2" clock. In QEMU, they are slow
> > only because of the division operation in
On Wed, 25 Aug 2021, Mark Cave-Ayland wrote:
> On 24/08/2021 11:09, Finn Thain wrote:
>
> > This code appears to be unnecessary.
> >
> > Signed-off-by: Finn Thain
> > ---
> > hw/misc/mos6522.c | 22 +-
> > 1 file changed, 1 insertion(+), 21 deletions(-)
> >
> > diff
On Wed, 25 Aug 2021, Mark Cave-Ayland wrote:
> On 24/08/2021 11:09, Finn Thain wrote:
>
> > The first reload of timer 1 is early by half of a clock cycle as it gets
> > measured from a falling edge. By contrast, the succeeding reloads are
> > measured from rising edge to rising edge.
> >
> >
Just noticed, I forgot to initialize get_irq for the AST2500. I didn’t notice
it because I hadn’t tested booting an image for -machine ast2500-evb. I’ll make
sure to test with images for all 3 chip revisions, then I’ll resubmit with
PATCH v2. I’ll wait a little while though, for comments on the
From: Peter Delevoryas
This change replaces the UART serial device initialization code with machine
configuration data, making it so that we have a single code path for console
UART initialization, but allowing different machines to use different
UART's. This is relevant because the Aspeed chips
From: Peter Delevoryas
The AST2500 uses different logic than the AST2600 for getting IRQ's.
This adds a virtual `get_irq` function to the Aspeed SOC class, so that
the shared initialization code in `hw/arm/aspeed.c` can retrieve IRQ's.
Signed-off-by: Peter Delevoryas
---
From: Peter Delevoryas
Fuji uses the AST2600, so it's very similar to `ast2600-evb`, but it has
a few slight differences, such as using UART1 for the serial console.
Signed-off-by: Peter Delevoryas
---
hw/arm/aspeed.c | 13 +
1 file changed, 13 insertions(+)
diff --git
From: Peter Delevoryas
This register address is not actually used anywhere, and the datasheet
specifies that it's zero-initialized by default anyways, but the address
is incorrect. This just corrects the address.
Fixes: e09cf36321f6 ("hw: aspeed_scu: Add AST2600 support")
Signed-off-by: Peter
From: Peter Delevoryas
UART5 is typically used as the default debug UART on the AST2600, but
UART1 is also designed to be a debug UART. All the AST2600 UART's have
semi-configurable clock rates through registers in the System Control
Unit (SCU), but only UART5 works out of the box with
From: Peter Delevoryas
Hello!
This patch series creates an Aspeed machine type for Facebook's OpenBMC
platform "fuji".
The first 2 commits do some refactoring, to allow Aspeed machines to
configure the first serial device. Most board configurations use UART5
for the console, but fuji uses
Include linux/fs.h to avoid the following build failure on uclibc or
musl raised since version 6.0.0:
../block/export/fuse.c: In function 'fuse_lseek':
../block/export/fuse.c:641:19: error: 'SEEK_HOLE' undeclared (first use in this
function)
641 | if (whence != SEEK_HOLE && whence !=
Igor,
I'm not sure if I should post v7 with the correction to the tables,
or await your guidance/feedback on v6.
Thanks,
eric
On 8/6/21 12:16 PM, Eric DeVolder wrote:
Well, I discovered today that running "make check" again resulted in
bios table mismatches. In looking into this further, I
> On Aug 26, 2021, at 3:11 PM, i...@bsdimp.com wrote:
>
> From: Warner Losh
>
> Factor out load_elf_sections and is_target_elf_binary out of
> load_elf_interp.
>
> Signed-off-by: Mikaël Urankar
> Signed-off-by: Stacey Son
> Signed-off-by: Warner Losh
> ---
> bsd-user/elfload.c | 350
On Fri, 27 Aug 2021, John Arbuckle wrote:
I was having a problem with missing video resolutions in my Mac OS 9 VM. When I
ran QEMU it gave no indication as to why these resolutions were missing. I found
out that the OpenFirmware VGA driver was not being loaded. To prevent anyone
from
going thru
On Fri, Aug 27, 2021 at 05:06:27PM +0800, Guoyi Tu wrote:
>
> Signed-off-by: Guoyi Tu
> ---
> qapi/trace.json | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Reviewed-by: Eric Blake
>
> diff --git a/qapi/trace.json b/qapi/trace.json
> index 47c68f04da..eedfded512 100644
> ---
On Fri, Aug 27, 2021 at 04:50:47PM +, Raphael Norwitz wrote:
> In the vhost-user-blk-test, as of now there is nothing stoping
stopping
> vhost-user-blk in QEMU writing to the socket right after forking off the
> storage daemon before it has a chance to come up properly, leaving the
> test
On Fri, Aug 27, 2021 at 04:50:35PM +, Raphael Norwitz wrote:
> This change adds a command line option to print a line to standard out
> when the storage daemon has completed initialization and is ready to
> serve client connections.
>
> This option will be used to resolve a hang in the
> On 26. Aug 2021, at 05:43, Srikar Dronamraju
> wrote:
>
> * Christian Zigotzky [2021-08-16 14:29:21]:
>
>
> Hi Christian,
>
>> I tested the RC6 of kernel 5.14 today and unfortunately the issue still
>> exists. We have figured out that only P5040 SoCs are affected. [1]
>> P5020 SoCs
We are on the way to implement internal-backup with fleecing scheme,
which includes backup job copying from fleecing block driver node
(which is target of copy-before-write filter) to final target of
backup. This job doesn't need own filter, as fleecing block driver node
is a kind of snapshot,
On Fri, Aug 27, 2021 at 07:58:10PM +0300, Vladimir Sementsov-Ogievskiy wrote:
> 27.08.2021 18:09, Eric Blake wrote:
> > According to the NBD spec, a server advertising
> > NBD_FLAG_CAN_MULTI_CONN promises that multiple client connections will
> > not see any cache inconsistencies: when properly
In the following patch we'll want to pass blk children to block-copy.
Const pointers are not enough. So, return non const pointer from
blk_root().
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
include/sysemu/block-backend.h | 2 +-
block/block-backend.c | 2 +-
2 files changed, 2
On 8/27/21 8:01 PM, Willian Rampazzo wrote:
> Hi, Phil,
>
> On Thu, Aug 26, 2021 at 1:49 PM Philippe Mathieu-Daudé
> wrote:
>>
>> Hi Peter,
>>
>> On 7/9/21 6:00 PM, Peter Maydell wrote:
>>> On Fri, 9 Jul 2021 at 16:33, Peter Maydell wrote:
On Thu, 8 Jul 2021 at 15:55, Philippe
Add helper that returns both status and output, to be used in the
following commit
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
tests/qemu-iotests/iotests.py | 4
1 file changed, 4 insertions(+)
diff --git a/tests/qemu-iotests/iotests.py b/tests/qemu-iotests/iotests.py
index
Introduce a new driver, that works in pair with copy-before-write to
improve fleecing.
Without fleecing driver, old fleecing scheme looks as follows:
[guest]
|
|root
v
[copy-before-write] -> [temp.qcow2] <--- [nbd export]
| target |
|file
Add function to wait for all intersecting requests.
To be used in the further commit.
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
include/block/reqlist.h | 8
block/reqlist.c | 8
2 files changed, 16 insertions(+)
diff --git a/include/block/reqlist.h
The last step to make new fleecing scheme work (see block/fleecing.h
for descritption) is to update copy-before-write filter:
If we detect that unfiltered target child is fleecing block driver, we
do:
- initialize shared FleecingState
- activate fleecing block driver with it
- do guest write
FleecingState represents state shared between copy-before-write filter
and upcoming fleecing block driver.
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
block/fleecing.h | 135 ++
block/fleecing.c | 182 ++
Add test for push backup with fleecing:
- start fleecing with copy-before-write filter
- start a backup job from temporary fleecing node to actual backup
target
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
tests/qemu-iotests/tests/image-fleecing | 121 ++--
As announced in previous commit, we need use write-unchanged operations
for fleecing, so that fleecing client may unshare writes if needed.
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
block/copy-before-write.c | 13 +++--
1 file changed, 11 insertions(+), 2 deletions(-)
diff --git
Hi all!
That continues "[PATCH RFC DRAFT 00/11] Make image fleecing more usable"
and supersedes "[PATCH v2 for-6.2 0/6] push backup with fleecing"
Supersedes: <20210804131750.127574-1-vsement...@virtuozzo.com>
Supersedes: <20210721140424.163701-1-vsement...@virtuozzo.com>
There several
We are going to complicate bitmap initialization in the further
commit. And in future, backup job will be able to work without filter
(when source is immutable), so we'll need same bitmap initialization in
copy-before-write filter and in backup job. So, it's reasonable to do
it in block-copy.
This will be used in the following commit to bring "incremental" mode
to copy-before-write filter.
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
include/block/block-copy.h | 2 +-
block/block-copy.c | 14 --
block/copy-before-write.c | 2 +-
3 files changed, 14
This brings "incremental" mode to copy-before-write filter: user can
specify bitmap so that filter will copy only "dirty" areas.
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
qapi/block-core.json | 10 +-
block/copy-before-write.c | 30 +-
2 files
Split intersecting-requests functionality out of block-copy to be
reused in copy-before-write filter.
Note: while being here, fix tiny typo in MAINTAINERS.
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
include/block/reqlist.h | 67 +++
block/block-copy.c | 116
Note that reads zero areas (not dirty in the bitmap) fails, that's
correct.
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
tests/qemu-iotests/tests/image-fleecing | 32 ++--
tests/qemu-iotests/tests/image-fleecing.out | 84 +
2 files changed, 108 insertions(+), 8
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
tests/qemu-iotests/tests/image-fleecing | 67 +--
tests/qemu-iotests/tests/image-fleecing.out | 74 -
2 files changed, 121 insertions(+), 20 deletions(-)
diff --git a/tests/qemu-iotests/tests/image-fleecing
That simplifies handling failure in existing code and in further new
usage of bdrv_merge_dirty_bitmap().
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
include/block/dirty-bitmap.h| 2 +-
block/dirty-bitmap.c| 9 +++--
block/monitor/bitmap-qmp-cmds.c | 5 +
3 files
We are going to implement push backup with fleecing scheme. This means
that backup job will be a fleecing user and therefore will not need
separate copy-before-write filter. Instead it will consider source as
constant unchanged drive. Of course backup will want to unshare writes
on source for this
Add a convenient function similar with bdrv_block_status() to get
status of dirty bitmap.
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
include/block/dirty-bitmap.h | 2 ++
include/qemu/hbitmap.h | 11 +++
block/dirty-bitmap.c | 6 ++
util/hbitmap.c |
Split block_copy_reset() out of block_copy_reset_unallocated() to be
used separately later.
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
include/block/block-copy.h | 1 +
block/block-copy.c | 21 +
2 files changed, 14 insertions(+), 8 deletions(-)
diff --git
> On Aug 27, 2021, at 1:53 PM, Jag Raman wrote:
>
> add the libvfio-user library as a submodule. build it as a cmake
> subproject.
>
> Signed-off-by: Elena Ufimtseva
> Signed-off-by: John G Johnson
> Signed-off-by: Jagannathan Raman
> ---
> configure| 11 +++
>
Forward remote device's interrupts to the guest
Signed-off-by: Elena Ufimtseva
Signed-off-by: John G Johnson
Signed-off-by: Jagannathan Raman
---
include/hw/remote/iohub.h | 2 ++
hw/remote/iohub.c | 5 +
hw/remote/vfio-user-obj.c | 30 ++
I was having a problem with missing video resolutions in my Mac OS 9 VM. When I
ran QEMU it gave no indication as to why these resolutions were missing. I found
out that the OpenFirmware VGA driver was not being loaded. To prevent anyone
from
going thru the same trouble I went thru I added
Hi, Phil,
On Thu, Aug 26, 2021 at 1:49 PM Philippe Mathieu-Daudé wrote:
>
> Hi Peter,
>
> On 7/9/21 6:00 PM, Peter Maydell wrote:
> > On Fri, 9 Jul 2021 at 16:33, Peter Maydell wrote:
> >>
> >> On Thu, 8 Jul 2021 at 15:55, Philippe Mathieu-Daudé
> >> wrote:
> >>>
> >>> Since v1:
> >>> -
Determine the BARs used by the PCI device and register handlers to
manage the access to the same.
Signed-off-by: Elena Ufimtseva
Signed-off-by: John G Johnson
Signed-off-by: Jagannathan Raman
---
hw/remote/vfio-user-obj.c | 95 +++
Define and register handlers for PCI config space accesses
Signed-off-by: Elena Ufimtseva
Signed-off-by: John G Johnson
Signed-off-by: Jagannathan Raman
---
hw/remote/vfio-user-obj.c | 44
hw/remote/trace-events| 2 ++
2 files changed, 46
On Fri, Aug 27, 2021 at 05:48:10PM +0100, Richard W.M. Jones wrote:
> On Fri, Aug 27, 2021 at 10:09:16AM -0500, Eric Blake wrote:
> > +# Parallel client connections are easier with libnbd than qemu-io:
> > +if ! (nbdsh --version) >/dev/null 2>&1; then
>
> I'm curious why the parentheses are
Store and load the device's state during migration. use libvfio-user's
handlers for this purpose
Signed-off-by: Elena Ufimtseva
Signed-off-by: John G Johnson
Signed-off-by: Jagannathan Raman
---
migration/savevm.h| 2 +
hw/remote/vfio-user-obj.c | 313
Setup a handler to run vfio-user context. The context is driven by
messages to the file descriptor associated with it - get the fd for
the context and hook up the handler with it
Signed-off-by: Elena Ufimtseva
Signed-off-by: John G Johnson
Signed-off-by: Jagannathan Raman
---
Define and register callbacks to manage the RAM regions used for
device DMA
Signed-off-by: Elena Ufimtseva
Signed-off-by: John G Johnson
Signed-off-by: Jagannathan Raman
---
hw/remote/vfio-user-obj.c | 50 +++
hw/remote/trace-events| 2 ++
2
Find the PCI device with specified id. Initialize the device context
with the QEMU PCI device
Signed-off-by: Elena Ufimtseva
Signed-off-by: John G Johnson
Signed-off-by: Jagannathan Raman
---
hw/remote/vfio-user-obj.c | 28
1 file changed, 28 insertions(+)
diff
create a context with the vfio-user library to run a PCI device
Signed-off-by: Elena Ufimtseva
Signed-off-by: John G Johnson
Signed-off-by: Jagannathan Raman
---
hw/remote/vfio-user-obj.c | 29 +
1 file changed, 29 insertions(+)
diff --git
Acceptance test for libvfio-user in QEMU
Signed-off-by: Elena Ufimtseva
Signed-off-by: John G Johnson
Signed-off-by: Jagannathan Raman
---
MAINTAINERS | 1 +
tests/acceptance/vfio-user.py | 94 +++
2 files changed, 95 insertions(+)
Hi,
This series depends on the following series from
Elena Ufimtseva :
[PATCH RFC v2 00/16] vfio-user implementation
Thank you for your feedback for the v1 patches!
https://www.mail-archive.com/qemu-devel@nongnu.org/msg825021.html
We have incorporated the following feedback from v1 of the
add the libvfio-user library as a submodule. build it as a cmake
subproject.
Signed-off-by: Elena Ufimtseva
Signed-off-by: John G Johnson
Signed-off-by: Jagannathan Raman
---
configure| 11 +++
meson.build | 28
.gitmodules
Define vfio-user object which is remote process server for QEMU. Setup
object initialization functions and properties necessary to instantiate
the object
Signed-off-by: Elena Ufimtseva
Signed-off-by: John G Johnson
Signed-off-by: Jagannathan Raman
---
qapi/qom.json | 20 ++-
Per Brad on IRC, this issue persists. Re-opening to move to GitLab.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1819289
Title:
Windows 95 and Windows 98 will not install or run
Status in QEMU:
> -Original Message-
> From: Markus Armbruster
> Sent: Thursday, August 26, 2021 9:51 PM
> To: qemu-devel@nongnu.org
> Cc: peter.mayd...@linaro.org; Sunil Muthuswamy ;
> Kamil Rytarowski ; Reinoud Zandijk
> ; Reinoud Zandijk ; Michael S .
> Tsirkin
> Subject: [EXTERNAL] [PULL 08/15]
27.08.2021 18:09, Eric Blake wrote:
According to the NBD spec, a server advertising
NBD_FLAG_CAN_MULTI_CONN promises that multiple client connections will
not see any cache inconsistencies: when properly separated by a single
flush, actions performed by one client will be visible to another
On Wed, Aug 04, 2021 at 09:43:25AM -0400, Michael S. Tsirkin wrote:
> On Wed, Aug 04, 2021 at 01:40:37PM +0100, Peter Maydell wrote:
> > Saw this intermittent as part of my ad-hoc CI test setup.
> > The backtrace says that the QEMU process has somehow hung
> > during 'realize' of the vhost-user
In the vhost-user-blk-test, as of now there is nothing stoping
vhost-user-blk in QEMU writing to the socket right after forking off the
storage daemon before it has a chance to come up properly, leaving the
test hanging forever. This intermittently hanging test has caused QEMU
automation failures
This change adds a command line option to print a line to standard out
when the storage daemon has completed initialization and is ready to
serve client connections.
This option will be used to resolve a hang in the vhost-user-blk-test.
Signed-off-by: Raphael Norwitz
---
On Fri, Aug 27, 2021 at 10:09:16AM -0500, Eric Blake wrote:
> +# Parallel client connections are easier with libnbd than qemu-io:
> +if ! (nbdsh --version) >/dev/null 2>&1; then
I'm curious why the parentheses are needed here?
> +export nbd_unix_socket
> +nbdsh -c '
> +import os
> +sock =
> On Aug 27, 2021, at 10:00 AM, Philippe Mathieu-Daudé wrote:
>
> On 8/27/21 4:56 PM, Warner Losh wrote:
>>> On Aug 26, 2021, at 10:47 PM, Philippe Mathieu-Daudé
>>> wrote:
>>>
>>> On 8/26/21 11:11 PM, i...@bsdimp.com wrote:
From: Warner Losh
cpu_copy shouldbe called when
> On Aug 27, 2021, at 9:58 AM, Philippe Mathieu-Daudé wrote:
>
> On 8/27/21 5:02 PM, Warner Losh wrote:
>>> On Aug 26, 2021, at 10:42 PM, Philippe Mathieu-Daudé
>>> wrote:
>>>
>>> On 8/26/21 11:11 PM, i...@bsdimp.com wrote:
From: Warner Losh
LOW_ELF_STACK doesn't exist on
On 8/27/21 4:56 PM, Warner Losh wrote:
>> On Aug 26, 2021, at 10:47 PM, Philippe Mathieu-Daudé wrote:
>>
>> On 8/26/21 11:11 PM, i...@bsdimp.com wrote:
>>> From: Warner Losh
>>>
>>> cpu_copy shouldbe called when processes are creating new threads. It
>>
>> Typo "should be"
>>
>>> copies the
On 8/27/21 5:02 PM, Warner Losh wrote:
>> On Aug 26, 2021, at 10:42 PM, Philippe Mathieu-Daudé wrote:
>>
>> On 8/26/21 11:11 PM, i...@bsdimp.com wrote:
>>> From: Warner Losh
>>>
>>> LOW_ELF_STACK doesn't exist on FreeBSD and likely never will. Remove it.
>>> Likewise, remove an #if 0 block
> On Aug 26, 2021, at 10:19 PM, Philippe Mathieu-Daudé wrote:
>
> On 8/26/21 11:11 PM, i...@bsdimp.com wrote:
>> From: Warner Losh
>>
>> Move the arcitecture specific defines to target_arch_elf.h and delete
>
> Typo "architecture"
Thanks
>> them from elfload.c. unifdef as appropriate for
On 8/27/21 5:17 PM, Thomas Huth wrote:
> libfdt in Debian is too old to be usable for QEMU. So far we were
> silently falling back to the internal dtc submodule, but since
> this is wrong, let's remove the --enable-fdt=system switch here now.
>
> Signed-off-by: Thomas Huth
> ---
> Sorry, I just
> On Aug 26, 2021, at 10:22 PM, Philippe Mathieu-Daudé wrote:
>
> On 8/26/21 11:11 PM, i...@bsdimp.com wrote:
>> From: Warner Losh
>>
>> Pass the bsd_param into loader_exec, and adjust.
>
> Missing the "why" justification.
So I am. I’ve added it and it will be in v3 of the patches. It’s
> On Aug 26, 2021, at 10:39 PM, Philippe Mathieu-Daudé wrote:
>
> On 8/26/21 11:11 PM, i...@bsdimp.com wrote:
>> From: Warner Losh
>>
>> Move the CPU functons into target_arch_cpu.c that are unique to each
>
> Typo "functions"
doh! Thanks!
>> CPU. These are defined in target_arch.h.
>>
`muldiv64` would overflow in cases where the final 96-bit value does not
fit in a `uint64_t`. This would result in small values that cause an
interrupt to be triggered much sooner than intended.
The overflow can be detected in most cases by checking if the new value is
smaller than the previous
On Fri, Aug 27, 2021 at 05:17:18PM +0200, Thomas Huth wrote:
> libfdt in Debian is too old to be usable for QEMU. So far we were
> silently falling back to the internal dtc submodule, but since
> this is wrong, let's remove the --enable-fdt=system switch here now.
>
> Signed-off-by: Thomas Huth
libfdt in Debian is too old to be usable for QEMU. So far we were
silently falling back to the internal dtc submodule, but since
this is wrong, let's remove the --enable-fdt=system switch here now.
Signed-off-by: Thomas Huth
---
Sorry, I just noticed this after sending out the first three
libfdt in Debian is too old to be usable for QEMU. So far we were
silently falling back to the internal dtc submodule, but since
this is wrong, let's remove the --enable-fdt=system switch here now.
Signed-off-by: Thomas Huth
---
Sorry, I just noticed this after sending out the first three
According to the NBD spec, a server advertising
NBD_FLAG_CAN_MULTI_CONN promises that multiple client connections will
not see any cache inconsistencies: when properly separated by a single
flush, actions performed by one client will be visible to another
client, regardless of which client did the
On Fri, Aug 27, 2021 at 03:14:36PM +0800, Song Gao wrote:
> +The following versions of the LoongArch core are supported
> +core: 3A5000
> +
> https://github.com/loongson/LoongArch-Documentation/releases/download/LoongArch-Vol1-v3/LoongArch-Vol1-v1.00-EN.pdf
This link seems invalid now.
> On Aug 26, 2021, at 10:42 PM, Philippe Mathieu-Daudé wrote:
>
> On 8/26/21 11:11 PM, i...@bsdimp.com wrote:
>> From: Warner Losh
>>
>> LOW_ELF_STACK doesn't exist on FreeBSD and likely never will. Remove it.
>> Likewise, remove an #if 0 block that's not useful
>>
>> Signed-off-by: Warner
> On Aug 26, 2021, at 10:47 PM, Philippe Mathieu-Daudé wrote:
>
> On 8/26/21 11:11 PM, i...@bsdimp.com wrote:
>> From: Warner Losh
>>
>> cpu_copy shouldbe called when processes are creating new threads. It
>
> Typo "should be"
>
>> copies the current state of the CPU to a new cpu state
> On Aug 26, 2021, at 10:48 PM, Philippe Mathieu-Daudé wrote:
>
> On 8/26/21 11:12 PM, i...@bsdimp.com wrote:
>> From: Colin Percival
>>
>> Previously it was impossible to emulate a program with a file name
>> different from its argv[0]. With this change, you can run
>>qemu -0 fakename
Signed-off-by: Guoyi Tu
---
qapi/trace.json | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/qapi/trace.json b/qapi/trace.json
index 47c68f04da..eedfded512 100644
--- a/qapi/trace.json
+++ b/qapi/trace.json
@@ -99,7 +99,7 @@
# Example:
#
# -> { "execute":
On Fri, Aug 27, 2021 at 11:51:04AM +0400, Marc-André Lureau wrote:
> Hi
>
> On Fri, Aug 27, 2021 at 11:44 AM Marc-André Lureau <
> marcandre.lur...@redhat.com> wrote:
>
> > Hi
> >
> > On Thu, Aug 26, 2021 at 10:58 PM Peter Xu wrote:
> >
> >> Both dump-guest-memory and live migration caches vm
On Tue, Aug 24, 2021 at 10:11:14AM +0100, Peter Maydell wrote:
> On Tue, 24 Aug 2021 at 00:05, Changbin Du wrote:
> >
> > On Mon, Aug 23, 2021 at 04:30:05PM +0100, Peter Maydell wrote:
> > > changes to be more capable of handling dynamic target changes
> > > (this would also help with eg
> >> Oh, I wasn't referring to any specific users. What I meant is that,
> >> if we make abs64() generically available from host-utils, callers
> >> could expect it to behave the same way as abs() in stdlib, for
> >> example.
> >
> > That would be surprising, but do you think there are cases where
On 8/5/21 3:57 PM, marcandre.lur...@redhat.com wrote:
> From: Marc-André Lureau
>
> Avoid handlers being called with dangling pointers when the object is
> freed.
>
> Signed-off-by: Marc-André Lureau
> ---
> ui/vdagent.c | 25 +++--
> 1 file changed, 15 insertions(+), 10
On Fri, Aug 27, 2021 at 3:14 AM Philippe Mathieu-Daudé wrote:
>
> Commit 155e1c82ed0 deprecated the raspi2/raspi3 machine names.
> Use the recommended new names: raspi2b and raspi3b.
>
> Signed-off-by: Philippe Mathieu-Daudé
> ---
> docs/devel/qgraph.rst | 38
On 8/5/21 3:56 PM, marcandre.lur...@redhat.com wrote:
> From: Marc-André Lureau
>
> "info" was leaked when more than 10 entries.
>
> Signed-off-by: Marc-André Lureau
> ---
> include/ui/clipboard.h | 2 ++
> ui/vdagent.c | 4 +---
> 2 files changed, 3 insertions(+), 3 deletions(-)
Hi Eric,
On Tue, Aug 17, 2021 at 04:58:01PM +0200, Eric Auger wrote:
> Hi Jean,
>
> On 8/10/21 10:45 AM, Jean-Philippe Brucker wrote:
> > Allow instantiating a virtio-iommu device on ACPI systems by adding a
> > Virtual I/O Translation table (VIOT). Enable x86 support for VIOT.
>
> Don't you
On Tue, Aug 10, 2021 at 11:22:27AM +0200, Igor Mammedov wrote:
> On Tue, 10 Aug 2021 10:45:02 +0200
> Jean-Philippe Brucker wrote:
>
> > Add a function that generates a Virtual I/O Translation table (VIOT),
> > describing the topology of paravirtual IOMMUs. The table is created when
> >
On Tue, Aug 17, 2021 at 03:42:22PM +0200, Eric Auger wrote:
> > diff --git a/hw/virtio/virtio-iommu-pci.c b/hw/virtio/virtio-iommu-pci.c
> > index 770c286be7..f30eb16cbf 100644
> > --- a/hw/virtio/virtio-iommu-pci.c
> > +++ b/hw/virtio/virtio-iommu-pci.c
> > @@ -48,16 +48,9 @@ static void
On Tue, Aug 17, 2021 at 04:11:49PM +0200, Eric Auger wrote:
> Hi Jean,
>
> On 8/10/21 10:45 AM, Jean-Philippe Brucker wrote:
> > From: Eric Auger
> >
> > Add a hotplug handler for virtio-iommu on x86 and set the necessary
> > reserved region property. On x86, the [0xfee0, 0xfeef] DMA
> >
Hi
On Thu, Aug 5, 2021 at 5:59 PM wrote:
> From: Marc-André Lureau
>
> Hi,
>
> Here is a few fixes I have collected while working on clipboard-related
> code.
>
> There are some obvious code improvements/fixes, and better handling of
> release &
> unregister to avoid dangling pointers and
On 8/27/21 2:09 PM, Thomas Huth wrote:
> If the users ran configure with --enable-libfdt=system, they likely did
> that on purpose. We should not silently fall back to the internal libfdt
> if the system libfdt is not usable, but report the problem with a proper
> message instead.
>
>
On Fri, Aug 27, 2021 at 4:13 PM Thomas Huth wrote:
> There are some issues in the checks for libfdt in meson.build which
> get fixed with the first two patches.
>
> And while we're at it, also update the dtc submodule to a proper release
> version (in the third patch).
>
> Thomas Huth (3):
>
Ping:
From: John Arbuckle
Date: Fri, 30 Jul 2021 10:18:56 -0400
Subject: [PATCH 2/2] ui/cocoa.m: Add ability to swap command/meta and options
keys
For users who are use to using a Macintosh keyboard having to use a PC keyboard
can be a pain because the Command/meta and Option/Alt keys are
ping
From: John Arbuckle
Date: Thu, 29 Jul 2021 14:41:57 -0400
Subject: [PATCH 1/2] ui/cocoa.m: Add full keyboard grab support
There are keyboard shortcuts that are vital for use in a guest that runs Mac OS.
These shortcuts are reserved for Mac OS use only which makes having the guest
see them
On 8/27/21 1:03 PM, Mark Cave-Ayland wrote:
> On 27/08/2021 11:14, Peter Maydell wrote:
>
>> On Fri, 27 Aug 2021 at 10:14, Mark Cave-Ayland
>> wrote:
>>> Ah so the plan moving forward is to always have an explicit MR passed
>>> in for DMA use.
>>> Sorry if I missed that in earlier versions of
The dtc submodule is currently pointing to non-release commit. It's nicer
if submodules point to release versions instead and since dtc 1.6.1 is
available now, let's update to that version.
Signed-off-by: Thomas Huth
---
dtc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
1 - 100 of 182 matches
Mail list logo
