Michael Tokarev writes:
> 05.09.2023 19:23, Peter Xu:
>> QEMU will crash if anyone tries to set tls-authz (which is a type
>> StrOrNull) with 'null' value. Fix it in the easy way by converting it to
>> qstring just like the other two tls parameters.
>
> Ping? Has this been forgotten?
Daniel P. Berrangé writes:
> On Wed, Sep 27, 2023 at 12:49:08PM -0400, James Bottomley wrote:
>> From: James Bottomley
>>
>> The Microsoft Simulator (mssim) is the reference emulation platform
>> for the TCG TPM 2.0 specification.
>>
>> https://github.com/Microsoft/ms-tpm-20-ref.git
>>
>> It
Wrong thread, please ignore.
On 28/08/2023 14.23, Thomas Huth wrote:
On 17/08/2023 19.09, Thomas Huth wrote:
On 17/08/2023 15.47, Marc-André Lureau wrote:
Hi
On Thu, Aug 17, 2023 at 5:06 PM Daniel P. Berrangé
wrote:
On Thu, Aug 17, 2023 at 02:00:26PM +0200, Thomas Huth wrote:
On 17/08/2023 12.32, Daniel P. Berrangé
On 27/09/2023 23.47, Fabiano Rosas wrote:
Add a smoke test that migrates to a file and gives it to the
script. It should catch the most annoying errors such as changes in
the ram flags.
After code has been merged it becomes way harder to figure out what is
causing the script to fail, the person
This property isn't meant to do much else besides return a list of
strings, so move this setup back out into _pre_launch().
Signed-off-by: John Snow
Reviewed-by: Ani Sinha
Reviewed-by: Daniel P. Berrangé
---
python/qemu/machine/machine.py | 5 ++---
1 file changed, 2 insertions(+), 3
Create a socketpair for the console output. This should help eliminate
race conditions around console text early in the boot process that might
otherwise have been dropped on the floor before being able to connect to
QEMU under "server,nowait".
Signed-off-by: John Snow
Reviewed-by: Ani Sinha
Like the QMP and console sockets, begin using socketpairs for the qtest
connection, too. After this patch, we'll be able to remove the vestigial
sock_dir argument, but that cleanup is best done in its own patch.
Signed-off-by: John Snow
Reviewed-by: Daniel P. Berrangé
---
Useful if we want to use ConsoleSocket() for a socket created by
socketpair().
Signed-off-by: John Snow
Reviewed-by: Ani Sinha
Reviewed-by: Daniel P. Berrangé
---
python/qemu/machine/console_socket.py | 29 +++
1 file changed, 21 insertions(+), 8 deletions(-)
diff
If everything has gone smoothly, we'll already have closed the socket we
gave to the child during post_launch. The other half of the pair that we
gave to the QMP connection should, likewise, be definitively closed by
now.
However, in the cleanup path, it's possible we've created the socketpair
By using a socketpair for all of the sockets managed by the VM class and
its extensions, we don't need the sock_dir argument anymore, so remove
it.
We only added this argument so that we could specify a second, shorter
temporary directory for cases where the temp/log dirs were "too long" as
a
Like we did for the QMP socket, use socketpair() for the console socket
so that hopefully there isn't a race condition during early boot where
data might get dropped on the floor.
May or may not help with various race conditions where early console
output is not showing up in the logs and/or
05.09.2023 19:23, Peter Xu:
QEMU will crash if anyone tries to set tls-authz (which is a type
StrOrNull) with 'null' value. Fix it in the easy way by converting it to
qstring just like the other two tls parameters.
Ping? Has this been forgotten?
Thanks,
/mjt
Cc: qemu-sta...@nongnu.org #
On 28/09/2023 05.45, Chris Rauer wrote:
Could you please add a proper patch description how this is fixing the issue?
Thanks,
Thomas
Fixes: https://gitlab.com/qemu-project/qemu/-/issues/1897
Signed-off-by: Chris Rauer
---
tests/qtest/npcm7xx_timer-test.c | 1 +
1 file changed, 1
Fixes: https://gitlab.com/qemu-project/qemu/-/issues/1897
Signed-off-by: Chris Rauer
---
tests/qtest/npcm7xx_timer-test.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/tests/qtest/npcm7xx_timer-test.c b/tests/qtest/npcm7xx_timer-test.c
index 43711049ca..58f58c2f71 100644
---
> On 27-Sep-2023, at 8:55 PM, Michael S. Tsirkin wrote:
>
> On Tue, Sep 26, 2023 at 11:22:35AM +0530, Ani Sinha wrote:
>> Code changes that addresses all compiler complaints coming from enabling
>> -Wshadow flags. Enabling -Wshadow catches cases of local variables shadowing
>> other local
> On Sep 27, 2023, at 3:27 PM, Stefan Hajnoczi wrote:
>
> vhost-user-scsi has a VirtioDeviceClass->reset() function that calls
> ->vhost_reset_device(). The other vhost devices don't notify the vhost
> device upon reset.
>
> Stateful vhost devices may need to handle device reset in order to
> On Sep 27, 2023, at 3:27 PM, Stefan Hajnoczi wrote:
>
> vhost_kernel_reset_device() invokes RESET_OWNER, which disassociates the
> owner process from the device. The device is left non-operational since
> SET_OWNER is only called once during startup in vhost_dev_init().
>
>
> On Sep 27, 2023, at 3:27 PM, Stefan Hajnoczi wrote:
>
> The VHOST_USER_RESET_OWNER message is deprecated in the spec:
>
> This is no longer used. Used to be sent to request disabling all
> rings, but some back-ends interpreted it to also discard connection
> state (this
Hi Eric, Matthew,
>-Original Message-
>From: Matthew Rosato
>Sent: Wednesday, September 27, 2023 9:26 PM
>Subject: Re: [PATCH v2 09/12] vfio/ccw: Use vfio_[attach/detach]_device
>
>On 9/27/23 8:09 AM, Duan, Zhenzhong wrote:
>>
>>
>>> -Original Message-
>>> From: Eric Auger
>>>
Hi Eric,
>-Original Message-
>From: Eric Auger
>Sent: Wednesday, September 27, 2023 9:14 PM
>Subject: Re: [PATCH v2 11/12] vfio/common: Introduce two kinds of VFIO device
>lists
>
>Hi Zhenzhong,
>On 9/26/23 13:32, Zhenzhong Duan wrote:
>> In VFIO subsystem, there are different VFIO
On 9/27/2023 0:18, Joao Martins wrote:
> Right now downtime_start is stored in MigrationState.
>
> In preparation to having more downtime timestamps during
> switchover, move downtime_start to an array namely, @timestamp.
>
> Add a setter/getter surrounding which timestamps to record,
> to make
Hi Michael S. Tsirkin:
On Tue, Sep 26, 2023 at 08:49:27PM +0800, lixianglai wrote:
Hi Salil Mehta via And Michael S. Tsirkin:
From: Michael S. Tsirkin
Sent: Tuesday, September 26, 2023 12:54 PM
To: Salil Mehta
Cc: xianglai li ; qemu-devel@nongnu.org; Bernhard
Beschow ; Salil Mehta ;
Hi Salil,
On 9/26/23 20:04, Salil Mehta wrote:
Support of vCPU Hotplug requires sequence of ACPI handshakes between Qemu and
Guest kernel when a vCPU is plugged or unplugged. Most of the AML code to
support these handshakes already exists. This AML need to be build during VM
init for ARM
On 9/26/23 20:04, Salil Mehta wrote:
CPUs Control device(\\_SB.PCI0) register interface for the x86 arch is based on
PCI and is IO port based and hence existing cpus AML code assumes _CRS objects
^^
Hi Salil,
On 9/26/23 20:04, Salil Mehta wrote:
ACPI CPU hotplug state (is_present=_STA.PRESENT, is_enabled=_STA.ENABLED) for
all the possible vCPUs MUST be initialized during machine init. This is done
during the creation of the GED device. VMM/Qemu MUST expose/fake the ACPI state
of the
Hi Salil,
On 9/26/23 20:04, Salil Mehta wrote:
Add CPU Hotplug event to the set of supported ged-events during the creation of
GED device during VM init. Also initialize the memory map for CPU Hotplug
^^
it can be dropped.
control device used in event
Hi Salil,
On 9/26/23 20:04, Salil Mehta wrote:
ACPI GED(as described in the ACPI 6.2 spec) can be used to generate ACPI events
when OSPM/guest receives an interrupt listed in the _CRS object of GED. OSPM
then maps or demultiplexes the event by evaluating _EVT method.
This change adds the
Hi Salil,
On 9/26/23 20:04, Salil Mehta wrote:
ACPI CPU Hotplug code assumes a virtual CPU is unplugged if the CPUState object
is absent in the list of ths possible CPUs(CPUArchIdList *possible_cpus)
maintained on per-machine basis. Use the earlier introduced qemu_present_cpu()
API to check
On 9/26/23 20:04, Salil Mehta wrote:
ACPI CPU hotplug related initialization should only happend if ACPI_CPU_HOTPLUG
support has been enabled for particular architecture. Add cpu_hotplug_hw_init()
stub to avoid compilation break.
Signed-off-by: Salil Mehta
---
hw/acpi/acpi-cpu-hotplug-stub.c
Hi Salil,
On 9/26/23 20:04, Salil Mehta wrote:
ACPI is required to interface QEMU with the guest. Roughly falls into below
cases,
1. Convey the possible vcpus config at the machine init time to the guest
using various DSDT tables like MADT etc.
2. Convey vcpu hotplug events to guest(using
On 9/26/23 20:04, Salil Mehta wrote:
CPU ctrl-dev MMIO region length could be used in ACPI GED (common ACPI code
across architectures) and various other architecture specific places. To make
these code places independent of compilation order, ACPI_CPU_HOTPLUG_REG_LEN
macro should be moved to a
Hi Salil,
On 9/26/23 20:04, Salil Mehta wrote:
GIC needs to be pre-sized with possible vcpus at the initialization time. This
is necessary because Memory regions and resources associated with GICC/GICR
etc cannot be changed (add/del/modified) after VM has inited. Also, GIC_TYPER
needs to be
On Mon, Sep 25, 2023 at 05:11:07PM +0100, Jonathan Cameron wrote:
> New CCI types that will be supported shortly do not have a single buffer
> used in both directions. As such, split it up. For CXL mailboxes the two
> pointers will be aliases of the same memory so all callbacks must allow
> for
Allow external devices to drive pca9552 input pins by adding
input GPIO's to the model. This allows a device to connect
its output GPIO's to the pca9552 input GPIO's.
In order for an external device to set the state of a pca9552
pin, the pin must first be configured for high impedance (LED
is
Fabiano Rosas writes:
> Add a smoke test that migrates to a file and gives it to the
> script. It should catch the most annoying errors such as changes in
> the ram flags.
>
> After code has been merged it becomes way harder to figure out what is
> causing the script to fail, the person making
Add a smoke test that migrates to a file and gives it to the
script. It should catch the most annoying errors such as changes in
the ram flags.
After code has been merged it becomes way harder to figure out what is
causing the script to fail, the person making the change is the most
likely to
On Mon, Sep 18, 2023 at 05:53:10PM +0800, Sam Li wrote:
> Add the specs for the zoned format feature of the qcow2 driver.
> The qcow2 file can be taken as zoned device and passed through by
> virtio-blk device or NVMe ZNS device to the guest given zoned
> information.
>
> Signed-off-by: Sam Li
>
The pca9552 INPUT0 and INPUT1 registers are supposed to
hold the logical values of the LED pins. A logical 0
should be seen in the INPUT0/1 registers for a pin when
its corresponding LSn bits are set to 0, which is also
the state needed for turning on an LED in a typical
usage scenario. Existing
On Wed, Sep 27, 2023 at 10:32:14AM +0200, Hanna Czenczek wrote:
> On 26.09.23 22:10, Stefan Hajnoczi wrote:
> > Hi Hanna,
> > I was thinking about how this could work without SUSPEND/RESUME. What
> > do you think of the following?
> >
> > 1. The front-end sends VHOST_USER_RESET_DEVICE (or
> >
Applied, thanks.
Please update the changelog at https://wiki.qemu.org/ChangeLog/8.2 for any
user-visible changes.
signature.asc
Description: PGP signature
Applied, thanks.
Please update the changelog at https://wiki.qemu.org/ChangeLog/8.2 for any
user-visible changes.
signature.asc
Description: PGP signature
marcandre.lur...@redhat.com writes:
> From: Marc-André Lureau
>
> Traceback (most recent call last):
> File "scripts/analyze-migration.py", line 605, in
> dump.read(dump_memory = args.memory)
> File "scripts/analyze-migration.py", line 542, in read
> section.read()
> File
vhost-user-scsi has a VirtioDeviceClass->reset() function that calls
->vhost_reset_device(). The other vhost devices don't notify the vhost
device upon reset.
Stateful vhost devices may need to handle device reset in order to free
resources or prevent stale device state from interfering after
The VHOST_USER_RESET_OWNER message is deprecated in the spec:
This is no longer used. Used to be sent to request disabling all
rings, but some back-ends interpreted it to also discard connection
state (this interpretation would lead to bugs). It is recommended
that back-ends either
vhost_kernel_reset_device() invokes RESET_OWNER, which disassociates the
owner process from the device. The device is left non-operational since
SET_OWNER is only called once during startup in vhost_dev_init().
vhost_kernel_reset_device() is never called so this latent bug never
appears. Get rid
Stateful vhost devices may need to free resources or clear device state upon
device reset. The vhost-user protocol has a VHOST_USER_RESET_DEVICE message for
this and vDPA has SET_STATUS 0, but only QEMU's vhost-user-scsi device actually
implements this today.
This patch series performs device
On Mon, Sep 25, 2023 at 05:11:06PM +0100, Jonathan Cameron wrote:
> Putting the pointer in the structure for command handling puts a single
> variable element inside an otherwise constant structure. Move it out as
> a directly passed variable and take the cxl_cmd structures constant.
>
>
On Mon, Sep 25, 2023 at 04:22:58PM +0100, Jonathan Cameron wrote:
> Rename the version not burried in the macro to cap_h.
The change looks good to me. Just one minor thing. why "version" get
involved here?
Fan
>
> Signed-off-by: Jonathan Cameron
> ---
>
> I had another instance of this in a
Daniel P. Berrangé writes:
> On Wed, Sep 27, 2023 at 12:49:08PM -0400, James Bottomley wrote:
>> From: James Bottomley
>>
>> The Microsoft Simulator (mssim) is the reference emulation platform
>> for the TCG TPM 2.0 specification.
>>
>> https://github.com/Microsoft/ms-tpm-20-ref.git
>>
>> It
Eric Blake writes:
> On Mon, Sep 18, 2023 at 04:41:40PM +0200, Markus Armbruster wrote:
>> All we do with the value of RDMAContext member @error_state is test
>> whether it's zero. Change to bool and rename to @errored.
>>
>> Signed-off-by: Markus Armbruster
>> ---
>> migration/rdma.c | 66
Eric Blake writes:
> On Mon, Sep 18, 2023 at 04:41:27PM +0200, Markus Armbruster wrote:
>> qemu_rdma_buffer_mergable() is semantically a predicate. It returns
>> int 0 or 1. Return bool instead.
>
> While at it, this would be a perfect time to s/mergable/mergeable/g
Will do, thanks!
Eric Blake writes:
> On Mon, Sep 18, 2023 at 04:41:24PM +0200, Markus Armbruster wrote:
>> When all we do with an Error we receive into a local variable is
>> propagating to somewhere else, we can just as well receive it there
>> right away.
>>
>> Signed-off-by: Markus Armbruster
>> ---
>>
On Mon, Sep 18, 2023 at 02:28:14PM -0300, Fabiano Rosas wrote:
> This series contains fixes for the two currently know failures that
> show up in migration tests plus a set of fixes for some theoretical
> race conditions around QEMUFile handling.
>
> Patch 1 addresses the issue found in the
This patch adds more drm-related ioctls to support userland OpenGL and
Vulkan drivers.
Signed-off-by: Xiongchuan Tan
---
linux-user/ioctls.h| 26 +++
linux-user/syscall_defs.h | 15 -
linux-user/syscall_types.h | 68 ++
3 files
This patch adds more Direct Rendering Manager ioctls to support
userland OpenGL and Vulkan drivers, in addition to existing
DRM_IOCTL_VERSION.
More device-specific ioctls are needed though, but they share the same
range from 0x40 to 0x9f. Adding these would break the current
ailable in the Git repository at:
>
> https://github.com/bkoppelmann/qemu.git tags/pull-tricore-20230927
>
> for you to fetch changes up to 32dd1f0b4bf5f38f37434b0c8fe6c8d86e093b2b:
>
> target/tricore: Change effective address (ea) to target
On Mon, Sep 18, 2023 at 04:41:40PM +0200, Markus Armbruster wrote:
> All we do with the value of RDMAContext member @error_state is test
> whether it's zero. Change to bool and rename to @errored.
>
> Signed-off-by: Markus Armbruster
> ---
> migration/rdma.c | 66
On 9/27/23 12:49, James Bottomley wrote:
From: James Bottomley
Instead of processing the tpmdev options using the old qemu options,
convert to the new visitor format which also allows the passing of
json on the command line.
Signed-off-by: James Bottomley
---
v4: add TpmConfiOptions
v5:
On Wed, Sep 27, 2023 at 12:49:08PM -0400, James Bottomley wrote:
> From: James Bottomley
>
> The Microsoft Simulator (mssim) is the reference emulation platform
> for the TCG TPM 2.0 specification.
>
> https://github.com/Microsoft/ms-tpm-20-ref.git
>
> It exports a fairly simple network socket
From: James Bottomley
Instead of processing the tpmdev options using the old qemu options,
convert to the new visitor format which also allows the passing of
json on the command line.
Signed-off-by: James Bottomley
---
v4: add TpmConfiOptions
v5: exit(0) for help
v7: adjust line lengths, free
From: James Bottomley
The Microsoft Simulator (mssim) is the reference emulation platform
for the TCG TPM 2.0 specification.
https://github.com/Microsoft/ms-tpm-20-ref.git
It exports a fairly simple network socket based protocol on two
sockets, one for command (default 2321) and one for
From: James Bottomley
The requested feedback was to convert the tpmdev handler to being json
based, which requires rethreading all the backends. The good news is
this reduced quite a bit of code (especially as I converted it to
error_fatal handling as well, which removes the return status
On Wed, 27 Sep 2023 15:03:09 +
Vikram Sethi wrote:
> > From: Alex Williamson
> > Sent: Wednesday, September 27, 2023 9:25 AM
> > To: Jason Gunthorpe
> > Cc: Jonathan Cameron ; Ankit Agrawal
> > ; David Hildenbrand ; Cédric Le
> > Goater ; shannon.zha...@gmail.com;
> >
On Wed, Sep 27, 2023 at 01:11:38PM -0300, Fabiano Rosas wrote:
> I've been dedicating time to reviewing migration patches already for a
> while. I'll continue to do so for the foreseeable future.
>
> Signed-off-by: Fabiano Rosas
Reviewed-by: Peter Xu
Thanks!
--
Peter Xu
On Mon, Sep 18, 2023 at 04:41:27PM +0200, Markus Armbruster wrote:
> qemu_rdma_buffer_mergable() is semantically a predicate. It returns
> int 0 or 1. Return bool instead.
While at it, this would be a perfect time to s/mergable/mergeable/g
>
> Signed-off-by: Markus Armbruster
> ---
>
On Mon, Sep 18, 2023 at 04:41:24PM +0200, Markus Armbruster wrote:
> When all we do with an Error we receive into a local variable is
> propagating to somewhere else, we can just as well receive it there
> right away.
>
> Signed-off-by: Markus Armbruster
> ---
>
> ret =
I've been dedicating time to reviewing migration patches already for a
while. I'll continue to do so for the foreseeable future.
Signed-off-by: Fabiano Rosas
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 355b1960ce..2f2fa60311 100644
---
On Wed, Sep 27, 2023 at 11:55:41AM +0300, Vladimir Sementsov-Ogievskiy wrote:
> On 25.09.23 22:22, Eric Blake wrote:
> > Upcoming additions to support NBD 64-bit effect lengths allow for the
> > possibility to distinguish between payload length (capped at 32M) and
> > effect length (64 bits,
On Fri, 22 Sept 2023 at 14:21, Michal Orzel wrote:
>
> On an attempt to access CNTPCT_EL0 from EL0 using a guest running on top
> of Xen, a trap from EL2 was observed which is something not reproducible
> on HW (also, Xen does not trap accesses to physical counter).
>
> This is because
On 9/27/23 17:41, Michael S. Tsirkin wrote:
> On Wed, Sep 27, 2023 at 04:06:41PM +0200, Ilya Maximets wrote:
>> On 9/25/23 20:04, Ilya Maximets wrote:
>>> On 9/25/23 16:32, Stefan Hajnoczi wrote:
On Fri, 25 Aug 2023 at 13:02, Ilya Maximets wrote:
>
> It was supposed to be a compiler
On 9/19/23 15:19, Laszlo Ersek wrote:
> The fw_cfg DMA write callback in ramfb prepares a new display surface in
> QEMU; this new surface is put to use ("swapped in") upon the next display
> update. At that time, the old surface (if any) is released.
>
> If the guest triggers the fw_cfg DMA write
On Wed, Sep 27, 2023 at 03:03:09PM +, Vikram Sethi wrote:
> > From: Alex Williamson
> > Sent: Wednesday, September 27, 2023 9:25 AM
> > To: Jason Gunthorpe
> > Cc: Jonathan Cameron ; Ankit Agrawal
> > ; David Hildenbrand ; Cédric Le
> > Goater ; shannon.zha...@gmail.com;
> >
On Wed, Sep 27, 2023 at 04:06:41PM +0200, Ilya Maximets wrote:
> On 9/25/23 20:04, Ilya Maximets wrote:
> > On 9/25/23 16:32, Stefan Hajnoczi wrote:
> >> On Fri, 25 Aug 2023 at 13:02, Ilya Maximets wrote:
> >>>
> >>> It was supposed to be a compiler barrier and it was a compiler barrier
> >>>
Reviewed-by: Stefan Hajnoczi
On Wed, 27 Sept 2023 at 10:00, Ilya Maximets wrote:
>
>
> Version 2:
> - Converted into a patch set adding a new patch that removes the
> 'next' argument. [Stefan]
> - Completely removing the barrier instead of changing into compiler
> barrier.
> From: Alex Williamson
> Sent: Wednesday, September 27, 2023 9:25 AM
> To: Jason Gunthorpe
> Cc: Jonathan Cameron ; Ankit Agrawal
> ; David Hildenbrand ; Cédric Le
> Goater ; shannon.zha...@gmail.com;
> peter.mayd...@linaro.org; a...@anisinha.ca; Aniket Agashe
> ; Neo Jia ; Kirti Wankhede
> ;
On Tue, Sep 26, 2023 at 11:22:35AM +0530, Ani Sinha wrote:
> Code changes that addresses all compiler complaints coming from enabling
> -Wshadow flags. Enabling -Wshadow catches cases of local variables shadowing
> other local variables or parameters. These makes the code confusing and/or
> adds
On Tue, Sep 26, 2023 at 12:38:44PM +, Salil Mehta wrote:
> Hi Michael,
>
> > From: Michael S. Tsirkin
> > Sent: Tuesday, September 26, 2023 1:08 PM
> >
> > On Tue, Sep 26, 2023 at 07:26:40PM +0800, lixianglai wrote:
> > >
> > > Hi, Michael S. Tsirkin :
> > > > On Tue, Sep 26, 2023 at
On Tue, Sep 26, 2023 at 08:49:27PM +0800, lixianglai wrote:
>
> Hi Salil Mehta via And Michael S. Tsirkin:
> > > From: Michael S. Tsirkin
> > > Sent: Tuesday, September 26, 2023 12:54 PM
> > > To: Salil Mehta
> > > Cc: xianglai li ; qemu-devel@nongnu.org; Bernhard
> > > Beschow ; Salil Mehta ;
On Tue, Sep 26, 2023 at 01:30:30PM +0100, Daniel P. Berrangé wrote:
> On Tue, Sep 26, 2023 at 07:54:04AM -0400, Michael S. Tsirkin wrote:
> > On Tue, Sep 26, 2023 at 11:45:19AM +, Salil Mehta wrote:
> > >
> > > > From: Michael S. Tsirkin
> > > > Sent: Tuesday, September 26, 2023 12:12 PM
> >
On Wed, Sep 27, 2023 at 03:36:16PM +0100, Daniel P. Berrangé wrote:
> Even if not actively sending a PR, a possible starting point that could
> be done today, would be for someone to put up a gitlab.com branch that
> contains all the outstanding patch series that are considered ready
> to merge
Convert docs/specs/edu.txt to rST format.
Signed-off-by: Peter Maydell
---
MAINTAINERS | 1 +
docs/specs/{edu.txt => edu.rst} | 84 -
docs/specs/index.rst| 1 +
3 files changed, 54 insertions(+), 32 deletions(-)
rename
This patchseries converts most of the remaining .txt files in
docs/specs to rST format and integrates tem with our documentation.
(The one remaining .txt file is rocker.txt, which I left to do
later because at over 1000 lines it is much bigger than these.)
These are mostly simple conversions with
Convert docs/specs/vmcoreinfo.txt to rST format.
Signed-off-by: Peter Maydell
---
MAINTAINERS | 1 +
docs/specs/index.rst | 1 +
docs/specs/{vmcoreinfo.txt => vmcoreinfo.rst} | 33 ++-
3 files changed, 19
Convert docs/specs/ivshmem-spec.txt to rST format.
In converting, I have dropped the sections on the device's command
line interface and usage, as they are already covered by the
user-facing docs in system/devices/ivshmem.rst.
I have also removed the reference to Memnic, because the URL is dead
Convert the docs/specs/vmw_pvscsi-spec.txt file to rST format.
This conversion includes some minor wordsmithing of the text
to fix some grammar nits.
Signed-off-by: Peter Maydell
---
The number of lines changed for markup formatting was
such a large amount of the document that it didn't seem
Convert docs/specs/standard-vga.txt to rST format.
Signed-off-by: Peter Maydell
---
docs/specs/index.rst| 1 +
docs/specs/standard-vga.rst | 94 +
docs/specs/standard-vga.txt | 81
hw/display/vga-isa.c| 2 +-
Convert docs/specs/vmgenid.txt to rST format.
Signed-off-by: Peter Maydell
---
MAINTAINERS| 2 +-
docs/specs/index.rst | 1 +
docs/specs/vmgenid.rst | 246 +
docs/specs/vmgenid.txt | 245
4 files
Convert docs/specs/virt-ctlr.txt to rST format.
I added the name of the device to give readers a bit more idea
of which device we're actually documenting here.
Signed-off-by: Peter Maydell
---
docs/specs/index.rst| 1 +
docs/specs/{virt-ctlr.txt => virt-ctlr.rst} | 12
Convert docs/specs/pvpanic.txt to rST format.
Signed-off-by: Peter Maydell
---
docs/specs/index.rst| 1 +
docs/specs/{pvpanic.txt => pvpanic.rst} | 41 -
2 files changed, 28 insertions(+), 14 deletions(-)
rename docs/specs/{pvpanic.txt =>
On Wed, 27 Sept 2023 at 15:40, Eric Blake wrote:
>
> From: Eric Blake
>
> Documenting that we should not add new lines to work around SPF
> rewrites sounds foreboding; the intent is instead that new lines here
> are okay, but indicate a second problem elsewhere in our build process
> that we
On Wed, Sep 27, 2023 at 09:38:18AM -0500, Eric Blake wrote:
> From: Eric Blake
>
> Documenting that we should not add new lines to work around SPF
> rewrites sounds foreboding; the intent is instead that new lines here
> are okay, but indicate a second problem elsewhere in our build process
>
On Wed, 27 Sept 2023 at 09:52, Ilya Maximets wrote:
>
> We do not need the most up to date number of heads, we only want to
> know if there is at least one.
>
> Use shadow variable as long as it is not equal to the last available
> index checked. This avoids expensive qatomic dereference of the
From: Eric Blake
Experimenting yet again, this time with an eye towards letting patchew
attribute the patch to my name rather than my email. Also, by sending
a series with more than one patch, I'm testing how authorship is
preserved. My editor window does not see a body From: line, but
From: Andrey Drobyshev
This fixes authorship of commits 2848289168, 52b10c9c0c as the mailing
list rewrote the "From:" field in the corresponding patches. See commit
3bd2608db7 ("maint: Add .mailmap entries for patches claiming list
authorship") for explanation.
Signed-off-by: Andrey Drobyshev
From: Eric Blake
Documenting that we should not add new lines to work around SPF
rewrites sounds foreboding; the intent is instead that new lines here
are okay, but indicate a second problem elsewhere in our build process
that we should also consider fixing at the same time, to keep the
section
From: Eric Blake
This fixes authorship of commits 5cbd51a5 and friends, where the
qemu-ppc mailing list rewrote the "From:" field in the corresponding
patches. See commit 3bd2608db7 ("maint: Add .mailmap entries for
patches claiming list authorship") for explanation.
Signed-off-by: Eric Blake
On Wed, Sep 27, 2023 at 09:56:44AM -0400, Peter Xu wrote:
> Juan will be back next Monday. Before he left, he told me that he's
> preparing the pull.
>
> If next week there's still no pull from migration side then I suppose
> someone should start to pick up patches and send PR. I would volunteer
On Wed, Sep 27, 2023 at 03:14:29PM +0200, Claudio Fontana wrote:
> On 9/13/23 15:00, Claudio Fontana wrote:
> > On 8/30/23 15:09, Claudio Fontana wrote:
> >> On 8/22/23 15:25, Philippe Mathieu-Daudé wrote:
> >>> Hi Claudio,
> >>>
> >>> On 22/8/23 14:00, Claudio Fontana wrote:
> Hello,
>
On Wed, 27 Sep 2023 10:53:36 -0300
Jason Gunthorpe wrote:
> On Wed, Sep 27, 2023 at 12:33:18PM +0100, Jonathan Cameron wrote:
>
> > CXL accelerators / GPUs etc are a different question but who has one
> > of those anyway? :)
>
> That's exactly what I mean when I say CXL will need it too. I
1 - 100 of 217 matches
Mail list logo
