Hi Connie,
On 10/26/22 7:10 PM, Cornelia Huck wrote:
On Wed, Oct 26 2022, Gavin Shan wrote:
On 10/25/22 6:54 PM, Cornelia Huck wrote:
On Mon, Oct 24 2022, Gavin Shan wrote:
These 3 high memory regions are usually enabled by default, but
s/These 3/The/ ?
Ok.
they may be not used. Fo
On Fri, Oct 28, 2022 at 4:44 AM Jason Wang wrote:
>
>
> 在 2022/10/27 04:58, Michael S. Tsirkin 写道:
> > On Thu, Oct 20, 2022 at 05:52:47PM +0200, Eugenio Pérez wrote:
> >> Event idx helps to reduce the number of notifications between the device
> >> and the driver. It allows them to specify an inde
Hi Connie,
On 10/26/22 6:43 PM, Cornelia Huck wrote:
On Wed, Oct 26 2022, Gavin Shan wrote:
On 10/26/22 12:29 AM, Eric Auger wrote:
On 10/24/22 05:54, Gavin Shan wrote:
There are three high memory regions, which are VIRT_HIGH_REDIST2,
VIRT_HIGH_PCIE_ECAM and VIRT_HIGH_PCIE_MMIO. Their base a
On Wed, Oct 26, 2022 at 01:46:20PM -0700, Isaku Yamahata wrote:
> On Tue, Oct 25, 2022 at 11:13:42PM +0800,
> Chao Peng wrote:
>
> > When private/shared memory are mixed in a large page, the lpage_info may
> > not be accurate and should be updated with this mixed info. A large page
> > has mixed
On Thu, Oct 27, 2022 at 11:27:05AM +0100, Fuad Tabba wrote:
> Hi,
>
> On Tue, Oct 25, 2022 at 4:19 PM Chao Peng wrote:
> >
> > This new KVM exit allows userspace to handle memory-related errors. It
> > indicates an error happens in KVM at guest memory range [gpa, gpa+size).
> > The flags includes
This patch introduce ECAP_PASID via "x-pasid-mode". Based on the
existing support for scalable mode, we need to implement the following
missing parts:
1) tag VTDAddressSpace with PASID and support IOMMU/DMA translation
with PASID
2) tag IOTLB with PASID
3) PASID cache and its flush
4) PASID bas
Hi All:
This series tries to introduce PASID support for Intel IOMMU. The work
is based on the previous scalabe mode support by implement the
ECAP_PASID. A new "x-pasid-mode" is introduced to enable this
mode. All internal vIOMMU codes were extended to support PASID instead
of the current RID2PASI
We used to have a macro for VTD_PE_GET_FPD_ERR() but it has an
internal goto which prevents it from being reused. This patch convert
that macro to a dedicated function and let the caller to decide what
to do (e.g using goto or not). This makes sure it can be re-used for
other function that requires
We introduce VTDBus structure as an intermediate step for searching
the address space. This works well with SID based matching/lookup. But
when we want to support SID plus PASID based address space lookup,
this intermediate steps turns out to be a burden. So the patch simply
drops the VTDBus struct
We use to warn on wrong rid2pasid entry. But this error could be
triggered by the guest and could happens during initialization. So
let's don't warn in this case.
Reviewed-by: Peter Xu
Signed-off-by: Jason Wang
---
Changes since v4:
- Tweak the code to avoid using ret variable
---
hw/i386/intel
When you try to set a property that has no setter, the error message
blames "insufficient permission":
$ qemu-system-x86_64 -S -display none -nodefaults -monitor stdio
QEMU 7.1.50 monitor - type 'help' for more information
(qemu) qom-set /machine type q35
Error: Insufficient permis
When you try to set qtest property "log" while the qtest object is
active, the error message blames "insufficient permission":
$ qemu-system-x86_64 -S -display none -nodefaults -monitor stdio -chardev
socket,id=chrqt0,path=qtest.socket,server=on,wait=off -object
qtest,id=qt0,chardev=chrqt0,l
When you try to set virtio-rng property "filename" after the backend
has been completed with user_creatable_complete(), the error message
blames "insufficient permission":
$ qemu-system-x86_64 -S -display none -nodefaults -monitor stdio -object
rng-random,id=rng0 -device virtio-rng,id=vrng0,r
Signed-off-by: Markus Armbruster
Message-Id: <20221012153801.2604340-5-arm...@redhat.com>
---
include/qapi/qmp/qerror.h | 3 ---
1 file changed, 3 deletions(-)
diff --git a/include/qapi/qmp/qerror.h b/include/qapi/qmp/qerror.h
index 596fce0c54..87ca83b155 100644
--- a/include/qapi/qmp/qerror.h
+
The following changes since commit 344744e148e6e865f5a57e745b02a87e5ea534ad:
Merge tag 'dump-pull-request' of https://gitlab.com/marcandre.lureau/qemu
into staging (2022-10-26 10:53:49 -0400)
are available in the Git repository at:
https://repo.or.cz/qemu/armbru.git tags/pull-error-2022-10-
From: Laurent Vivier
As qemu_opts_parse_noisily() flattens the QAPI structures ("type" field
of Netdev structure can collides with "type" field of SocketAddress),
we introduce a way to bypass qemu_opts_parse_noisily() and use directly
visit_type_Netdev() to parse the backend parameters.
More det
From: Laurent Vivier
Embed the setting of info_str in a function.
Signed-off-by: Laurent Vivier
Reviewed-by: David Gibson
Acked-by: Michael S. Tsirkin
Reviewed-by: Philippe Mathieu-Daudé
Signed-off-by: Jason Wang
---
hw/net/xen_nic.c | 5 ++---
include/net/net.h | 1 +
net/l2tpv3.c
From: Laurent Vivier
The only caller passes &error_fatal, so use this directly in the function.
It's what we do for -blockdev, -device, and -object.
Suggested-by: Markus Armbruster
Signed-off-by: Laurent Vivier
Reviewed-by: Markus Armbruster
Reviewed-by: David Gibson
Acked-by: Michael S. Ts
From: Stefano Brivio
Other errors are treated as failure by net_socket_connect_init(),
but if connect() returns EINVAL, we'll fail silently. Remove the
related exception.
Signed-off-by: Stefano Brivio
Signed-off-by: Laurent Vivier
Reviewed-by: David Gibson
Acked-by: Michael S. Tsirkin
Signed
From: Laurent Vivier
Signed-off-by: Laurent Vivier
Reviewed-by: Stefano Brivio
Reviewed-by: David Gibson
Acked-by: Michael S. Tsirkin
Signed-off-by: Jason Wang
---
include/qemu/sockets.h | 2 ++
net/net.c | 62 ++
2 files changed
From: Laurent Vivier
Rename SocketAddress_to_str() to socket_uri() and move it to
util/qemu-sockets.c close to socket_parse().
socket_uri() generates a string from a SocketAddress while
socket_parse() generates a SocketAddress from a string.
Signed-off-by: Laurent Vivier
Reviewed-by: David Gib
From: Laurent Vivier
Use QIOChannel, QIOChannelSocket and QIONetListener.
This allows net/stream to use all the available parameters provided by
SocketAddress.
Signed-off-by: Laurent Vivier
Acked-by: Michael S. Tsirkin
Signed-off-by: Jason Wang
---
net/stream.c| 492 -
From: Eugenio Pérez
The guest will see undefined behavior if it issue not negotiate
commands, bit it is expected somehow.
Simplify code deleting this check.
Signed-off-by: Eugenio Pérez
Acked-by: Jason Wang
Signed-off-by: Jason Wang
---
net/vhost-vdpa.c | 48
From: Si-Wei Liu
Similar to other vhost backends, vhostfd can be passed to vhost-vdpa
backend as another parameter to instantiate vhost-vdpa net client.
This would benefit the use case where only open file descriptors, as
opposed to raw vhost-vdpa device paths, are accessible from the QEMU
proces
From: Laurent Vivier
Signed-off-by: Laurent Vivier
Reviewed-by: Stefano Brivio
Acked-by: Michael S. Tsirkin
Acked-by: Markus Armbruster (QAPI schema)
Reviewed-by: Philippe Mathieu-Daudé
Signed-off-by: Jason Wang
---
net/stream.c| 107
From: Stefano Brivio
Other errors are treated as failure by net_stream_client_init(),
but if connect() returns EINVAL, we'll fail silently. Remove the
related exception.
Signed-off-by: Stefano Brivio
[lvivier: applied to net/stream.c]
Signed-off-by: Laurent Vivier
Reviewed-by: Daniel P. Berran
From: Laurent Vivier
To be consistent with socket_uri(), add 'tcp:' prefix for inet type in
socket_parse(), by default socket_parse() use tcp when no prefix is
provided (format is host:port).
In socket_uri(), use 'vsock:' prefix for vsock type rather than 'tcp:'
because it makes a vsock address
From: Laurent Vivier
All net_client_parse() callers exit in case of error.
Move exit(1) to net_client_parse() and remove error checking from
the callers.
Suggested-by: Markus Armbruster
Signed-off-by: Laurent Vivier
Reviewed-by: Markus Armbruster
Reviewed-by: David Gibson
Acked-by: Michael
From: Eugenio Pérez
This entry was duplicated on referenced commit. Removing it.
Fixes: 402378407dbd ("vhost-vdpa: multiqueue support")
Signed-off-by: Eugenio Pérez
Acked-by: Jason Wang
Signed-off-by: Jason Wang
---
net/vhost-vdpa.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/net/vhos
From: Eugenio Pérez
There was not enough room to accomodate them.
Reviewed-by: Michael S. Tsirkin
Signed-off-by: Eugenio Pérez
Signed-off-by: Jason Wang
---
hw/virtio/vhost-shadow-virtqueue.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/hw/virtio/vhost-shadow-v
From: Eugenio Pérez
Actually use the new field of the used ring and tell the device if SVQ
wants to be notified.
The code is not reachable at the moment.
Reviewed-by: Michael S. Tsirkin
Signed-off-by: Eugenio Pérez
Signed-off-by: Jason Wang
---
hw/virtio/vhost-shadow-virtqueue.c | 18 ++
From: Laurent Vivier
Copied from socket netdev file and modified to use SocketAddress
to be able to introduce new features like unix socket.
"udp" and "mcast" are squashed into dgram netdev, multicast is detected
according to the IP address type.
"listen" and "connect" modes are managed by strea
From: Eugenio Pérez
So SVQ code knows if an event is needed.
The code is not reachable at the moment.
Reviewed-by: Michael S. Tsirkin
Signed-off-by: Eugenio Pérez
Signed-off-by: Jason Wang
---
hw/virtio/vhost-shadow-virtqueue.c | 12 +++-
1 file changed, 11 insertions(+), 1 deletion
From: Laurent Vivier
It is less complex to manage special cases directly in
net_dgram_mcast_init() and net_dgram_udp_init().
Signed-off-by: Laurent Vivier
Reviewed-by: Stefano Brivio
Acked-by: Michael S. Tsirkin
Signed-off-by: Jason Wang
---
net/dgram.c | 143 +++
From: Eugenio Pérez
Enabling all the code path created before.
Reviewed-by: Michael S. Tsirkin
Signed-off-by: Eugenio Pérez
Signed-off-by: Jason Wang
---
hw/virtio/vhost-shadow-virtqueue.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/hw/virtio/vhost-shadow-virtqueue.c
b/hw/virtio/vho
From: Laurent Vivier
dgram_dst is a sockaddr_in structure. To be able to use it with
unix socket, use a pointer to a generic sockaddr structure.
Rename it dest_addr, and store socket length in dest_len.
Signed-off-by: Laurent Vivier
Reviewed-by: Stefano Brivio
Acked-by: Michael S. Tsirkin
Re
The following changes since commit 344744e148e6e865f5a57e745b02a87e5ea534ad:
Merge tag 'dump-pull-request' of https://gitlab.com/marcandre.lureau/qemu
into staging (2022-10-26 10:53:49 -0400)
are available in the git repository at:
https://github.com/jasowang/qemu.git tags/net-pull-request
From: Laurent Vivier
Signed-off-by: Laurent Vivier
Reviewed-by: Stefano Brivio
Reviewed-by: David Gibson
Acked-by: Michael S. Tsirkin
Acked-by: Markus Armbruster (QAPI schema)
Signed-off-by: Jason Wang
---
net/dgram.c | 55 ++-
qapi/n
From: Daniel P. Berrangé
The current message when using '-net user...' with SLIRP disabled at
compile time is:
qemu-system-x86_64: -net user: Parameter 'type' expects a net backend type
(maybe it is not compiled into this binary)
An observation is that we're using the 'netdev->type' field he
From: Laurent Vivier
When virtio_net_flush_tx() reaches the tx_burst value all
the queue is not flushed and nothing restart the timer.
Fix that by doing for TX timer as we do for bottom half TX:
rearming the timer if we find any packet to send during the
virtio_net_flush_tx() call.
Fixes: e3f30
From: Laurent Vivier
The netdev reports NETDEV_STREAM_CONNECTED event when the backend
is connected, and NETDEV_STREAM_DISCONNECTED when it is disconnected.
The NETDEV_STREAM_CONNECTED event includes the destination address.
This allows a system manager like libvirt to detect when the server
fa
From: Laurent Vivier
When virtio-net is used with the socket netdev backend, the backend
can be busy and not able to collect new packets.
In this case, net_socket_receive() returns 0 and registers a poll function
to detect when the socket is ready again.
In virtio_net_tx_bh(), virtio_net_flush_
I pulled 7.1, and the megasas driver stopped being able to do reads
from a disk.
It looks to be related to this commit:
https://github.com/qemu/qemu/commit/fe9d8927e265fd723a6dc87cd6d220f4677dbe1f#diffe3f5f30efc54747e0624dca63e5f55f0012736c1875b6e85526b3514e6911be3
which added some comm
Now that we have fixed various test case issues as seen when running
on Windows, let's enable the qtest build on Windows.
Signed-off-by: Bin Meng
Reviewed-by: Thomas Huth
---
Changes in v5:
- Drop patches that are already merged
Changes in v3:
- Drop the host test
Changes in v2:
- new patch:
Some qtest cases don't get response from the QEMU executable under
test in time on Windows. It turns out that the socket receive call
got timeout before it receive the complete response.
The timeout value is supposed to be set to 50 seconds via the
setsockopt() call, but there is a difference amon
In preparation to adding virtio-9p support on Windows, this series
enables running qtest on Windows, so that we can run the virtio-9p
tests on Windows to make sure it does not break accidently.
Changes in v6:
- drop patches that are already in Alex and Daniel's tree
- remove CONFIG_POSIX from meso
在 2022/10/21 17:09, Laurent Vivier 写道:
Signed-off-by: Laurent Vivier
Acked-by: Michael S. Tsirkin
---
I got this:
63/63 ERROR:../tests/qtest/netdev-socket.c:139:test_stream_inet_ipv6:
assertion failed (resp == expect): ("st0: index=0,type=stream,connection
error\r\n" == "st0: index=0,ty
From: Xuzhou Cheng
Make sure QEMU process "to" exited before launching another target
for migration in the test_multifd_tcp_cancel case.
Signed-off-by: Xuzhou Cheng
Signed-off-by: Bin Meng
---
Changes in v6:
- change to use qtest_wait_qemu() API
Changes in v3:
- Add a usleep(1) in the busy
From: Xuzhou Cheng
Currently signal SIGIPI [=SIGUSR1] is used to kick the dummy CPU
when qtest accelerator is used. However SIGUSR1 is unsupported on
Windows. To support Windows, we add a QemuSemaphore CPUState::sem
to kick the dummy CPU instead for Windows.
Signed-off-by: Xuzhou Cheng
Signed-o
At present the virtio-9p related codes are built into libqos
unconditionally. Change to build them conditionally by testing
the 'virtfs' config option.
Signed-off-by: Bin Meng
---
Changes in v6:
- new patch: "test/qtest/libqos: meson.build: Do not build virtio-9p
unconditionally"
tests/qtest
When migration fails, QEMU exits with a status code EXIT_FAILURE.
Change qtests to use the well-defined macro instead of magic number.
Signed-off-by: Bin Meng
---
Changes in v6:
- new patch: "tests/qtest: Use EXIT_FAILURE instead of magic number"
tests/qtest/dbus-vmstate-test.c | 2 +-
tests/
The usage of double/single quotes in test_q35_pci_unplug_json_request()
should be reversed to work on both win32 and non-win32 platforms:
- The value of -device parameter needs to be surrounded by "" as
Windows does not drop '' when passing it to QEMU which causes
QEMU command line option pars
commit 9f8e6cad65a6 ("gitlab-ci: Speed up the msys2-64bit job by using
--without-default-devices"
changed to compile QEMU with the --without-default-devices switch for
the msys2-64bit job, due to the build could not complete within the
project timeout (1h), and also mentioned that a bigger timeout
At present the libqtest codes were written to depend on several
POSIX APIs, including fork(), kill() and waitpid(). Unfortunately
these APIs are not available on Windows.
This commit implements the corresponding functionalities using
win32 native APIs. With this change, all qtest cases can build
s
Introduce an API for qtest to wait for the QEMU process to terminate.
Suggested-by: Marc-André Lureau
Signed-off-by: Bin Meng
---
Changes in v6:
- new patch: "tests/qtest: libqtest: Introduce qtest_wait_qemu()"
tests/qtest/libqtest.h | 9 ++
tests/qtest/libqtest.c | 63 +
From: Xuzhou Cheng
Socket communication in the libqtest and libqmp codes uses read()
and write() which work on any file descriptor on *nix, and sockets
in *nix are an example of a file descriptor.
However sockets on Windows do not use *nix-style file descriptors,
so read() and write() cannot be
Peter Maydell writes:
> On Thu, 27 Oct 2022 at 18:17, Markus Armbruster wrote:
>>
>> Peter Maydell writes:
>>
>> > On Thu, 27 Oct 2022 at 15:40, Markus Armbruster wrote:
>> >> I wonder why we use any of .def, .h.inc, .inc.h, .c.inc, .inc.c. Why
>> >> not .h and call it a day? No need to conf
>-Original Message-
>From: Duan, Zhenzhong
>Sent: Friday, July 22, 2022 4:46 PM
>To: qemu-devel@nongnu.org
>Cc: pbonz...@redhat.com; pet...@redhat.com; da...@redhat.com;
>f4...@amsat.org
>Subject: [PATCH v2] softmmu/physmem: Fix input parameters for
>flatview_access_allowed()
>
>The com
在 2022/10/27 04:58, Michael S. Tsirkin 写道:
On Thu, Oct 20, 2022 at 05:52:47PM +0200, Eugenio Pérez wrote:
Event idx helps to reduce the number of notifications between the device
and the driver. It allows them to specify an index on the circular
descriptors rings where to issue the notificatio
On Fri, 28 Oct 2022 10:23:16 +0800
Jason Wang wrote:
> On Fri, Oct 28, 2022 at 10:08 AM Alex Williamson
> wrote:
> >
> > On Fri, 28 Oct 2022 09:50:10 +0800
> > Jason Wang wrote:
> >
> > > On Fri, Oct 28, 2022 at 5:11 AM Alex Williamson
> > > wrote:
> > > >
> > > > On Thu, 27 Oct 2022 15:40
On Fri, Oct 28, 2022 at 10:35 AM Alex Williamson
wrote:
>
> On Fri, 28 Oct 2022 10:23:16 +0800
> Jason Wang wrote:
>
> > On Fri, Oct 28, 2022 at 10:08 AM Alex Williamson
> > wrote:
> > >
> > > On Fri, 28 Oct 2022 09:50:10 +0800
> > > Jason Wang wrote:
> > >
> > > > On Fri, Oct 28, 2022 at 5:11
On Fri, Oct 28, 2022 at 12:31 AM Christian Schoenebeck
wrote:
>
> On Thursday, October 27, 2022 6:19:27 PM CEST Bin Meng wrote:
> > Hi Christian,
> >
> > On Mon, Oct 24, 2022 at 1:16 PM Bin Meng wrote:
> > >
> > > At present there is no Windows support for 9p file system.
> > > This series adds i
On Fri, Oct 28, 2022 at 10:08 AM Alex Williamson
wrote:
>
> On Fri, 28 Oct 2022 09:50:10 +0800
> Jason Wang wrote:
>
> > On Fri, Oct 28, 2022 at 5:11 AM Alex Williamson
> > wrote:
> > >
> > > On Thu, 27 Oct 2022 15:40:31 +0800
> > > Cindy Lu wrote:
> > >
> > > > Move the function vfio_get_xlat_
>-Original Message-
>From: David Hildenbrand
>Sent: Friday, July 22, 2022 2:44 PM
>To: Duan, Zhenzhong ; qemu-
>de...@nongnu.org
>Cc: pbonz...@redhat.com; pet...@redhat.com; f4...@amsat.org
>Subject: Re: [PATCH] memory: Fix wrong end address dump
>
>On 22.06.22 11:59, Zhenzhong Duan wrot
On Fri, 28 Oct 2022 09:50:10 +0800
Jason Wang wrote:
> On Fri, Oct 28, 2022 at 5:11 AM Alex Williamson
> wrote:
> >
> > On Thu, 27 Oct 2022 15:40:31 +0800
> > Cindy Lu wrote:
> >
> > > Move the function vfio_get_xlat_addr to softmmu/memory.c, and
> > > change the name to memory_get_xlat_addr(
On Thu, Oct 27, 2022 at 9:16 PM Yi Liu wrote:
>
> On 2022/10/27 15:50, Jason Wang wrote:
> > We used to have a macro for VTD_PE_GET_FPD_ERR() but it has an
> > internal goto which prevents it from being reused. This patch convert
> > that macro to a dedicated function and let the caller to decide
On Thu, Oct 27, 2022 at 9:20 PM Yi Liu wrote:
>
> On 2022/10/27 15:50, Jason Wang wrote:
> > We use to warn on wrong rid2pasid entry. But this error could be
> > triggered by the guest and could happens during initialization. So
> > let's don't warn in this case.
> >
> > Signed-off-by: Jason Wang
On Thu, Oct 27, 2022 at 6:52 PM Daniel P. Berrangé wrote:
>
> ping: Jason, are you willing to queue this since it has two
> positive reviews.
>
Yes, I've queued this.
Thanks
> On Mon, Oct 03, 2022 at 11:06:12AM +0100, Daniel P. Berrangé wrote:
> > The current message when using '-net user...' w
On Thu, Oct 27, 2022 at 6:18 PM Eugenio Perez Martin
wrote:
>
> On Thu, Oct 27, 2022 at 8:54 AM Jason Wang wrote:
> >
> > On Thu, Oct 27, 2022 at 2:47 PM Eugenio Perez Martin
> > wrote:
> > >
> > > On Thu, Oct 27, 2022 at 6:32 AM Jason Wang wrote:
> > > >
> > > >
> > > > 在 2022/10/26 17:53, Eug
On Fri, Oct 28, 2022 at 5:56 AM Si-Wei Liu wrote:
>
> Hi Jason,
>
> Sorry for top posting, but are you going to queue this patch? It looks
> like the discussion has been settled and no further comment I got for 2
> weeks for this patch.
Yes, I've queued this.
Thanks
>
> Thanks,
> -Siwei
>
> On
On Fri, Oct 28, 2022 at 5:11 AM Alex Williamson
wrote:
>
> On Thu, 27 Oct 2022 15:40:31 +0800
> Cindy Lu wrote:
>
> > Move the function vfio_get_xlat_addr to softmmu/memory.c, and
> > change the name to memory_get_xlat_addr().So we can use this
> > function in other devices,such as vDPA device.
>
This series load FDT table into dram memory space
and add uart,rtc info into FDT, Add TPM device for
LoongArch virt machine.
Changes for v2:
1. Modify the title of the first patch("Change FDT base")
to "Load FDT table into dram memory space".
Changes for v1:
1. Change FDT base addr to 2 MiB.
Add TPM device for LoongArch virt machine, including
establish TPM acpi info and add TYPE_TPM_TIS_SYSBUS
to dynamic_sysbus_devices list.
Signed-off-by: Xiaojuan Yang
---
hw/loongarch/acpi-build.c | 50 +--
hw/loongarch/virt.c | 4
2 files changed,
Add new items into LoongArch FDT, including rtc and uart info.
Signed-off-by: Xiaojuan Yang
---
hw/loongarch/virt.c| 31 +++
include/hw/pci-host/ls7a.h | 1 +
2 files changed, 32 insertions(+)
diff --git a/hw/loongarch/virt.c b/hw/loongarch/virt.c
index fe33
Load FDT table into dram memory space, and the addr is 2 MiB.
Since lowmem region starts from 0, FDT base address is located
at 2 MiB to avoid NULL pointer access.
Signed-off-by: Xiaojuan Yang
---
hw/loongarch/virt.c | 18 +++---
include/hw/loongarch/virt.h | 3 ---
2 files
On 10/10/2022 10:49 AM, Ilya Oleinik wrote:
> For EBX bits 23 - 16 in CPUID[01] Intel's manual states:
> "
> * The nearest power-of-2 integer that is not smaller than EBX[23:16]
> is the number of unique initial APICIDs reserved for addressing
> different logical processors in a physica
On Thu, Oct 27, 2022 at 3:50 PM Mayuresh Chitale
wrote:
>
> Currently the ISA string for a CPU is generated from two different
> arrays, one for single letter extensions and another for multi letter
> extensions. Add all the single letter extensions to the isa_ext_data
> array and use it for gener
Hi Daniel, Bernhard,
On 27/10/22 11:47, Daniel Henrique Barboza wrote:
On 10/27/22 05:21, Bernhard Beschow wrote:
Am 16. September 2022 14:36:05 UTC schrieb "Philippe Mathieu-Daudé"
:
On 12/9/22 21:50, Bernhard Beschow wrote:
Am 1. September 2022 11:41:14 UTC schrieb Bernhard Beschow
:
Tes
On 27/10/22 12:26, Richard Henderson wrote:
The helpers for reset_rf, cli, sti, clac, stac are
completely trivial; implement them inline.
Drop some nearby #if 0 code.
Signed-off-by: Richard Henderson
---
target/i386/helper.h| 5 -
target/i386/tcg/cc_helper.c | 41 --
On 26/10/22 15:31, Bernhard Beschow wrote:
Resolving the PIIX ISA bridge rather than the PIIX ACPI controller mirrors
the ICH9 code one line below.
Signed-off-by: Bernhard Beschow
---
hw/i386/acpi-build.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Reviewed-by: Philippe Mathieu-D
On 26/10/22 15:31, Bernhard Beschow wrote:
The code currently assumes Q35 iff ICH9 and i440fx iff PIIX. This is
slightly confusing when trying to understand the code. Split north and
south bridge code to communicate which piece of code assumes which type
of bridge.
Signed-off-by: Bernhard Bescho
Hi Jason,
Sorry for top posting, but are you going to queue this patch? It looks
like the discussion has been settled and no further comment I got for 2
weeks for this patch.
Thanks,
-Siwei
On 10/13/2022 4:12 PM, Si-Wei Liu wrote:
Jason,
On 10/12/2022 10:02 PM, Jason Wang wrote:
在 2022/1
On 26/10/22 15:31, Bernhard Beschow wrote:
The is_piix4 attribute is set once in one location and read once in
another. Doing both in one location allows for removing the attribute
altogether.
Signed-off-by: Bernhard Beschow
---
hw/i386/acpi-build.c | 20 ++--
1 file changed,
On 27/10/22 22:47, Philippe Mathieu-Daudé wrote:
Since v1:
- bswap -> tswap (Bernhard)
Bernhard posted a series merging both PIIX3/PIIX4 models
in one [1]. Due to Malta-specific board code forced into
the PIIX4 reset values, Bernhard had to include an array
of "register values at reset" as a cla
Hi Bernhard,
On 18/10/22 23:01, Bernhard Beschow wrote:
Will allow e500 boards to access SD cards using just their own devices.
Signed-off-by: Bernhard Beschow
---
hw/sd/sdhci.c | 120 +-
include/hw/sd/sdhci.h | 3 ++
2 files changed, 122 i
On 10/28/22 01:59, Alex Bennée wrote:
I'm unwilling to put an expensive test like a function call
(have_mmap_lock) before an inexpensive test like pointer != NULL.
Is it really that more expensive?
Well, yes. I mean, the function call isn't really slow, but it isn't single-cycle like a
comp
Revert the control and flag bits in the subchannel status word in case
the SSCH operation fails with non-zero CC (ditto for CSCH and HSCH).
According to POPS, the control and flag bits are only changed if SSCH,
CSCH, and HSCH return CC 0, and no other action should be taken otherwise.
In order to s
On 10/28/22 04:36, Alex Bennée wrote:
Convert another two dockerfiles to lcitool and update. I renamed the
helper because it is not Debian specific. We need an updated lcitool
for this to deal with the weirdness of a 32bit nsis tool for both 32
and 64 bit builds. As a result there are some minor
On 10/28/22 04:36, Alex Bennée wrote:
We originally naively treated expansion as safe because we expected
each new CPU/thread to appear in order. However the -M raspi2 model
triggered a case where a new high cpu_index thread started executing
just before a smaller one.
Clean this up by convertin
On 18/10/22 23:01, Bernhard Beschow wrote:
Adds missing functionality to e500plat machine which increases the
chance of given "real" firmware images to access SD cards.
Signed-off-by: Bernhard Beschow
---
docs/system/ppc/ppce500.rst | 12
hw/ppc/Kconfig | 1 +
hw/
On Thu, 27 Oct 2022 15:40:31 +0800
Cindy Lu wrote:
> Move the function vfio_get_xlat_addr to softmmu/memory.c, and
> change the name to memory_get_xlat_addr().So we can use this
> function in other devices,such as vDPA device.
>
> Signed-off-by: Cindy Lu
> ---
> hw/vfio/common.c | 92 ++--
On 18/10/22 23:01, Bernhard Beschow wrote:
Allows e500 boards to have their root file system reside on flash using
only builtin devices located in the eLBC memory region.
Note that the flash memory area is only created when a -pflash argument is
given, and that the size is determined by the give
On 10/28/22 00:44, Ilya Leoshkevich wrote:
Putting CPUJumpCache inside CPUState made problem go away:
diff --git a/include/hw/core/cpu.h b/include/hw/core/cpu.h
index 18ca701b443..3ea528566c3 100644
--- a/include/hw/core/cpu.h
+++ b/include/hw/core/cpu.h
@@ -32,6 +32,7 @@
#include "qemu/thread
On 22/10/22 17:04, Bernhard Beschow wrote:
Suggested-by: Mark Cave-Ayland
Signed-off-by: Bernhard Beschow
---
hw/i386/pc_piix.c | 3 ++-
hw/i386/pc_q35.c | 13 +++--
hw/isa/piix4.c| 2 +-
hw/usb/hcd-uhci.c | 16
hw/usb/hcd-uhci.h | 9 +
5 files ch
On Thu, Oct 27, 2022, 1:45 PM Christian Schoenebeck
wrote:
> On Thursday, October 27, 2022 7:37:07 PM CEST Stefan Hajnoczi wrote:
> > On Thu, 27 Oct 2022 at 12:38, Christian Schoenebeck
> > wrote:
> > >
> > > On Thursday, October 27, 2022 5:53:47 PM CEST Thomas Huth wrote:
> > > > On 24/10/2022
The PIIX4 PCI-ISA bridge function is always located at 10:0.
Since we want to re-use its address, add the PIIX4_PCI_DEVFN
definition.
Signed-off-by: Philippe Mathieu-Daudé
---
hw/mips/malta.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/hw/mips/malta.c b/hw/mips/malta.c
Linux kernel expects the northbridge & southbridge chipsets
configured by the BIOS firmware. We emulate that by writing
a tiny bootloader code in write_bootloader().
Upon introduction in commit 5c2b87e34d ("PIIX4 support"),
the PIIX4 configuration space included values specific to
the Malta board.
IRQRC[A:D] registers reset value is 0x80. We were forcing
the MIPS Malta machine routing to be able to boot a Linux
kernel without any bootloader.
We now have these registers initialized in the Malta machine
write_bootloader(), so we can use the correct reset values.
Signed-off-by: Philippe Mathie
Since v1:
- bswap -> tswap (Bernhard)
Bernhard posted a series merging both PIIX3/PIIX4 models
in one [1]. Due to Malta-specific board code forced into
the PIIX4 reset values, Bernhard had to include an array
of "register values at reset" as a class property. This
is not wrong, but to model proper
On 10/28/22 00:18, Ilya Leoshkevich wrote:
in one of the wasmtime tests (host=x86_64, guest=s390x).
GDB shows that the root cause is actually this:
Thread 181 "wasi_tokio::pat" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x76c54640 (LWP 168352)]
0x555
1 - 100 of 419 matches
Mail list logo
