On Fri, Oct 30, 2020 at 2:06 AM Eduardo Habkost wrote:
> This setter is one of the very few property setters that don't
> check dev->realized, and there's no reason to make size
> properties different from the rest. Add the missing check.
>
> Fixes: e8cd45c78f53 ("qdev: Add SIZE type to qdev pro
Hi Dmitry,
On 10/30/20 3:32 AM, Dmitry Fomichev wrote:
> The emulation code has been changed to advertise NVM Command Set when
> "zoned" device property is not set (default) and Zoned Namespace
> Command Set otherwise.
>
> Define values and structures that are needed to support Zoned
> Namespace
On 10/29/20 8:57 PM, Richard Henderson wrote:
> On 10/28/20 12:22 PM, Philippe Mathieu-Daudé wrote:
>> +g_autofree void *dtb;
>>
>> dtb = load_device_tree(dtb_filename, &dtb_size);
>
> With g_autofree, we must initialize the variable on declaration. Often this
> is
> w
Sigh, I should have caught some of these in the last review, sorry.
For the series,
Reviewed-by: Darren Kenny
Thanks,
Darren.
On Thursday, 2020-10-29 at 13:28:57 -04, Alexander Bulekov wrote:
> These patches fix some silly issues I found after the generic-fuzzer
> started running on OSS-Fuzz.
On Fri, Oct 30, 2020 at 2:07 AM Eduardo Habkost wrote:
> Make the code more generic and not specific to TYPE_DEVICE.
>
> Signed-off-by: Eduardo Habkost
>
Nice cleanup!, but fails to build atm
../hw/block/xen-block.c:403:9: error: ‘dev’ undeclared (first use in this
function); did you mean ‘vde
On Fri, Oct 30, 2020 at 11:29 AM Marc-André Lureau <
marcandre.lur...@gmail.com> wrote:
>
>
> On Fri, Oct 30, 2020 at 2:07 AM Eduardo Habkost
> wrote:
>
>> Make the code more generic and not specific to TYPE_DEVICE.
>>
>> Signed-off-by: Eduardo Habkost
>>
>
> Nice cleanup!, but fails to build at
On Fri, Oct 30, 2020 at 2:05 AM Eduardo Habkost wrote:
> An empty props array is unnecessary, we can just not call
> device_class_set_props().
>
> Signed-off-by: Eduardo Habkost
>
Reviewed-by: Marc-André Lureau
--
Marc-André Lureau
On Fri, Oct 30, 2020 at 2:07 AM Eduardo Habkost wrote:
> There's no reason to keep the property list separate from the CPU
> class code. Move the variable to hw/core/cpu.c and make it
> static.
>
> Signed-off-by: Eduardo Habkost
>
Reviewed-by: Marc-André Lureau
--
Marc-André Lureau
On Fri, Oct 30, 2020 at 2:05 AM Eduardo Habkost wrote:
> Move everything related to Property and PropertyInfo to
> qdev-properties.[ch] to make it easier to refactor that code.
>
> Signed-off-by: Eduardo Habkost
>
Reviewed-by: Marc-André Lureau
--
Marc-André Lureau
On Fri, Oct 30, 2020 at 2:07 AM Eduardo Habkost wrote:
> sparc_set_nwindows() is one of the very few property setters that
> don't check dev->realized, and there's no reason for it to be
> special. Check dev->realized like the other setters.
>
> Signed-off-by: Eduardo Habkost
>
Reviewed-by: Ma
On Fri, Oct 30, 2020 at 2:09 AM Eduardo Habkost wrote:
> Make the code more generic and not specific to TYPE_DEVICE.
>
> Signed-off-by: Eduardo Habkost
>
Reviewed-by: Marc-André Lureau
--
Marc-André Lureau
On Fri, Oct 30, 2020 at 2:05 AM Eduardo Habkost wrote:
> All other qdev property error messages use "."
> instead of ".". Change set_size32() for consistency,
> and to make the code not specific to TYPE_DEVICE.
>
> Signed-off-by: Eduardo Habkost
>
Reviewed-by: Marc-André Lureau
--
Marc-An
On Fri, Oct 30, 2020 at 2:09 AM Eduardo Habkost wrote:
> Make the code more generic and not specific to TYPE_DEVICE.
>
> Signed-off-by: Eduardo Habkost
>
Reviewed-by: Marc-André Lureau
--
Marc-André Lureau
On Fri, Oct 30, 2020 at 2:11 AM Eduardo Habkost wrote:
> Make the code more generic and not specific to TYPE_DEVICE.
>
> Signed-off-by: Eduardo Habkost
>
Reviewed-by: Marc-André Lureau
--
Marc-André Lureau
> A migration compatibility interface has not been determined for vfio.
> We currently rely on the vendor drivers to provide their own internal
> validation and harmlessly reject migration from an incompatible device.
> It would be great if we could make progress on this, but it's a
> difficult pro
On Fri, Oct 30, 2020 at 2:14 AM Eduardo Habkost wrote:
> Make the code more generic and not specific to TYPE_DEVICE.
>
> Signed-off-by: Eduardo Habkost
>
Reviewed-by: Marc-André Lureau
--
Marc-André Lureau
Hi,
The "Scalable Work Submission in Device Virtualization" talk at KVM
Forum 2020 was interesting and I have some beginner questions about
ENQCMD:
https://static.sched.com/hosted_files/kvmforum2020/22/Scalable_Work_Submission_In_Device_Virtualization.pdf
Security
If the ENQCMD instructio
On Fri, Oct 30, 2020 at 2:16 AM Eduardo Habkost wrote:
> Make the code more generic and not specific to TYPE_DEVICE.
>
> Signed-off-by: Eduardo Habkost
>
What about dropping _qdev from the function name too?
Also, I am not sure it's a well designed function.. I would rather have 3
different he
> From: Stefan Hajnoczi
> Sent: Friday, October 30, 2020 3:51 PM
>
> Hi,
> The "Scalable Work Submission in Device Virtualization" talk at KVM
> Forum 2020 was interesting and I have some beginner questions about
> ENQCMD:
> https://static.sched.com/hosted_files/kvmforum2020/22/Scalable_Work_Su
>
On Fri, Oct 30, 2020 at 2:10 AM Eduardo Habkost wrote:
> Every single qdev property setter function manually checks
> dev->realized. We can just check dev->realized inside
> qdev_property_set() instead.
>
> The check is being added as a separate function
> (qdev_prop_allow_set()) because it will
On Fri, Oct 30, 2020 at 2:11 AM Eduardo Habkost wrote:
> We'll add extra code to the qdev property getters and setters, so
> add wrapper functions where additional actions can be performed.
>
> The new functions have a "static_prop_" prefix instead of "qdev_"
> because the code will eventually be
This patch adds some gen_io_start() calls to allow execution
of s390x targets in icount mode with -smp 1.
It enables deterministic timers and record/replay features.
Signed-off-by: Pavel Dovgalyuk
---
0 files changed
diff --git a/target/s390x/translate.c b/target/s390x/translate.c
index ac10f42
On Mon, Sep 28, 2020 at 09:17:31PM +0800, Jiajun Chen wrote:
> Used_memslots is equal to dev->mem->nregions now, it is true for
> vhost kernel, but not for vhost user, which uses the memory regions
> that have file descriptor. In fact, not all of the memory regions
> have file descriptor.
> It is u
Fixes two bugs with the 9pfs 'local' tests as discussed with latest 9P PR
(2020-10-23). See the discussion of that PR for details.
Christian Schoenebeck (2):
tests/9pfs: fix test dir for parallel tests
tests/9pfs: fix coverity error in create_local_test_dir()
tests/qtest/libqos/virtio-9p.c |
Use mkdtemp() to generate a unique directory for the 9p 'local' tests.
This fixes occasional 9p test failures when running 'make check -jN' if
QEMU was compiled for multiple target architectures, because the individual
architecture's test suites would run in parallel and interfere with each
other'
Coverity wants the return value of mkdir() to be checked, so let's
pretend to do that. We're actually just making a dummy check and
ignore the result, because we actually only care if the required
directory exists and we have an existence check for that in place
already.
Reported-by: Greg Kurz
Si
On Mon, Oct 26, 2020 at 02:21:26PM +0800, Cindy Lu wrote:
> Sometime vdpa get an all 0 mac address from the hardware, this will cause the
> traffic down
> So we add the check for this part.
> if we get an 0 mac address we will use the default mac address instead
>
> Signed-off-by: Cindy Lu
> ---
On Mon, Oct 26, 2020 at 02:21:26PM +0800, Cindy Lu wrote:
> Sometime vdpa get an all 0 mac address from the hardware, this will cause the
> traffic down
> So we add the check for this part.
> if we get an 0 mac address we will use the default mac address instead
>
> Signed-off-by: Cindy Lu
I wo
Paolo Bonzini writes:
> On 29/10/20 14:38, Markus Armbruster wrote:
>> +/* Linux abstract socket */
>> +addr->u.q_unix.path = g_strndup(su->sun_path + 1,
>> +sizeof(su->sun_path) - 1);
>> +addr->u.q_unix.has_abstract = true;
>> +
On Mon, Sep 21, 2020 at 06:10:43PM -0400, Eduardo Habkost wrote:
> Class properties make QOM introspection simpler and easier, as
> they don't require an object to be instantiated.
>
> Signed-off-by: Eduardo Habkost
Reviewed-by: Michael S. Tsirkin
> ---
> Cc: "Michael S. Tsirkin"
> Cc: Marce
On Mon, Sep 21, 2020 at 06:10:26PM -0400, Eduardo Habkost wrote:
> Class properties make QOM introspection simpler and easier, as
> they don't require an object to be instantiated.
>
> Signed-off-by: Eduardo Habkost
Reviewed-by: Michael S. Tsirkin
> ---
> Cc: "Michael S. Tsirkin"
> Cc: qemu-d
On Wed, Sep 30, 2020 at 10:32:42AM +0530, P J P wrote:
>
> [+Paolo, +Fam Zheng - for scsi]
>
> +-- On Mon, 28 Sep 2020, P J P wrote --+
> | +-- On Wed, 16 Sep 2020, Peter Maydell wrote --+
> | | On Wed, 16 Sep 2020 at 07:28, P J P wrote:
> | | > ->
> https://ruhr-uni-bochum.sciebo.de/s/NNWP2Gfw
Eric Blake writes:
> On 10/29/20 8:38 AM, Markus Armbruster wrote:
>> Commit 776b97d360 "qemu-sockets: add abstract UNIX domain socket
>> support" neglected to update socket_sockaddr_to_address_unix(). The
>> function returns a non-abstract socket address for abstract
>> sockets (wrong) with a n
On Fri, Oct 30, 2020 at 4:55 PM Michael S. Tsirkin wrote:
>
> On Mon, Oct 26, 2020 at 02:21:26PM +0800, Cindy Lu wrote:
> > Sometime vdpa get an all 0 mac address from the hardware, this will cause
> > the traffic down
> > So we add the check for this part.
> > if we get an 0 mac address we will
Eric Blake writes:
> On 10/29/20 8:38 AM, Markus Armbruster wrote:
>> Commit 776b97d360 "qemu-sockets: add abstract UNIX domain socket
>> support" neglected to update qemu_chr_socket_address(). It shows
>> shows neither @abstract nor @tight. Fix that.
>>
>> Signed-off-by: Markus Armbruster
>>
On Thu, Oct 29, 2020 at 06:17:37PM +0100, Max Reitz wrote:
> RFC: https://www.redhat.com/archives/virtio-fs/2020-May/msg00024.html
> v1: https://lists.nongnu.org/archive/html/qemu-devel/2020-09/msg03598.html
>
> Branch: https://github.com/XanClic/qemu.git virtiofs-submounts-v3
> Branch: https://gi
On 29.10.20 21:46, Eduardo Habkost wrote:
> On Thu, Oct 29, 2020 at 06:17:44PM +0100, Max Reitz wrote:
>> This test invokes several shell scripts to create a random directory
>> tree full of submounts, and then check in the VM whether every submount
>> has its own ID and the structure looks as expe
On Thu, Oct 29, 2020 at 01:47:02PM -0500, Eric Blake wrote:
> On 10/29/20 11:07 AM, Kevin Wolf wrote:
>
> >>>
> >>> QEMU's interface is differently messy.
> >>>
> >>> Our equivalent to struct sockaddr_un is QAPI type UnixSocketAddress:
> >>>
> >>> { 'struct': 'UnixSocketAddress',
> >>> '
On Thu, Oct 29, 2020 at 12:01:27PM -0400, John Snow wrote:
> In experimenting with my mirror on gitlab though, I was unable to find a way
> to configure it to send issue tracker notifications to the email list. A
> move to gitlab would likely mean, then:
>
> 1. The cessation of (automatic) issue t
On Fri, Oct 30, 2020 at 8:58 AM Xinhao Zhang wrote:
>
> Fix code style. Space required before the open parenthesis '('.
>
> Signed-off-by: Xinhao Zhang
> Signed-off-by: Kai Deng
> Reported-by: Euler Robot
> ---
> target/riscv/csr.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
Rev
On Thu, Oct 29, 2020 at 04:27:44PM -0400, John Snow wrote:
> On 10/29/20 3:55 PM, Thomas Huth wrote:
> > On 29/10/2020 18.12, John Snow wrote:
> > > On 10/29/20 12:49 PM, Alistair Francis wrote:
> > > > On Thu, Oct 29, 2020 at 9:41 AM Cornelia Huck wrote:
> > > > >
> > > > > On Thu, 29 Oct 2020 1
Eric Blake writes:
> On 10/29/20 8:38 AM, Markus Armbruster wrote:
>> The abstract socket namespace is a non-portable Linux extension. An
>> attempt to use it elsewhere should fail with ENOENT (the abstract
>> address looks like a "" pathname, which does not resolve). We report
>> this failure
On Fri, Oct 30, 2020 at 12:02:18PM +0800, Antti Antinoja wrote:
> Hi All,
>
> I couldn't find any mention about live migration incompatibility between 5.0
> and 5.1 in the release notes but at least on our AMD based platform live
> migration from 5.0 to 5.1 is not possible.
>
> The upgraded hos
On Thu, Oct 29, 2020 at 04:25:41PM +0800, Bin Meng wrote:
> From: Bin Meng
>
> At present the virtio device config space access is handled by the
> virtio_config_readX() and virtio_config_writeX() APIs. They perform
> a sanity check on the result of address plus size against the config
> space si
Looking at the way the code is formatted here (there is an empty
line after break statements, but none where the break is missing),
the fallthrough is very likely intended here. So add a fallthrough
comment to make the it compilable with -Werror=implicit-fallthrough.
Signed-off-by: Thomas Huth
--
On 2020/10/30 上午11:04, Alex Williamson wrote:
On Fri, 30 Oct 2020 09:11:23 +0800
Jason Wang wrote:
On 2020/10/29 下午11:46, Alex Williamson wrote:
On Thu, 29 Oct 2020 23:09:33 +0800
Jason Wang wrote:
On 2020/10/29 下午10:31, Alex Williamson wrote:
On Thu, 29 Oct 2020 21:02:05 +0800
Jason
On Thu, Oct 29, 2020 at 02:38:28PM +0100, Markus Armbruster wrote:
> The test covers only two out of nine combinations. Test all nine.
> Four turn out to be broken. Marked /* BUG */.
>
> Signed-off-by: Markus Armbruster
> ---
> tests/test-util-sockets.c | 86 ---
On Thu, Oct 29, 2020 at 02:38:25PM +0100, Markus Armbruster wrote:
> The thread functions build the SocketAddress from global variable
> @abstract_sock_name and the tight flag passed as pointer
> argument (either NULL or (gpointer)1). There is no need for such
> hackery; simply pass the SocketAddr
On Fri, Oct 30, 2020 at 2:13 AM Eduardo Habkost wrote:
> Support Property.set_default and PropertyInfo.description even if
> PropertyInfo.create is set.
>
> Signed-off-by: Eduardo Habkost
> ---
> Cc: Paolo Bonzini
> Cc: "Daniel P. Berrangé"
> Cc: Eduardo Habkost
> Cc: qemu-devel@nongnu.org
>
On 2020/10/30 下午2:21, Stefan Hajnoczi wrote:
On Fri, Oct 30, 2020 at 3:04 AM Alex Williamson
wrote:
It's great to revisit ideas, but proclaiming a uAPI is bad solely
because the data transfer is opaque, without defining why that's bad,
evaluating the feasibility and implementation of defining
Le 30/10/2020 à 01:40, Chen Qun a écrit :
> When using -Wimplicit-fallthrough in our CFLAGS, the compiler showed warning:
> linux-user/mips/cpu_loop.c: In function ‘cpu_loop’:
> linux-user/mips/cpu_loop.c:104:24: warning: this statement may fall through
> [-Wimplicit-fallthrough=]
> 104 |
Hi
On Fri, Oct 30, 2020 at 2:19 AM Eduardo Habkost wrote:
> qdev_class_add_property() and qdev_property_add_static() will
> have code that's specific for device types.
>
> object_class_property_add_static(),
> object_class_add_static_props(), and object_property_add_static()
> will be generic an
On Thu, 29 Oct 2020 at 20:38, Eduardo Habkost wrote:
>
> Fix bounds check for idx at freq_to_str(), to actually ensure idx
> never goes beyond the last element of the suffixes array.
>
> Reported-by: Coverity (CID 1435957: OVERRUN)
> Suggested-by: Peter Maydell
Personally I preferred the other o
On Fri, Oct 30, 2020 at 2:18 AM Eduardo Habkost wrote:
> We're just doing pointer math with the device pointer, we can
> simply use obj instead.
>
> Signed-off-by: Eduardo Habkost
>
Reviewed-by: Marc-André Lureau
---
> Cc: Paolo Bonzini
> Cc: "Daniel P. Berrangé"
> Cc: Eduardo Habkost
> C
On Fri, Oct 30, 2020 at 2:17 AM Eduardo Habkost wrote:
> The array property registration code is hard to follow. Move the
> two steps into separate functions that have clear
> responsibilities.
>
> Signed-off-by: Eduardo Habkost
> ---
> Cc: Paolo Bonzini
> Cc: "Daniel P. Berrangé"
> Cc: Eduar
On Fri, 30 Oct 2020 at 09:23, Daniel P. Berrangé wrote:
> My convincing strategy is "do nothing" :-)
I am, er, not convinced :-)
> Most importantly we need to be able to make the existing "QEMU" component
> in launch read-only to prevent people filing new bugs there, ideally with
> a change in t
On Fri, Oct 30, 2020 at 10:03:44AM +, Peter Maydell wrote:
> On Fri, 30 Oct 2020 at 09:23, Daniel P. Berrangé wrote:
> > My convincing strategy is "do nothing" :-)
>
> I am, er, not convinced :-)
>
> > Most importantly we need to be able to make the existing "QEMU" component
> > in launch re
On Fri, Oct 30, 2020 at 2:03 PM Marc-André Lureau <
marcandre.lur...@gmail.com> wrote:
>
>
> On Fri, Oct 30, 2020 at 2:17 AM Eduardo Habkost
> wrote:
>
>> The array property registration code is hard to follow. Move the
>> two steps into separate functions that have clear
>> responsibilities.
>>
Marc-André Lureau writes:
> Hi Markus,
>
> On Thu, Oct 29, 2020 at 5:43 PM Markus Armbruster wrote:
>
>> In my opinion, the Linux-specific abstract UNIX domain socket feature
>> introduced in 5.1 should have been rejected. The feature is niche,
>> the interface clumsy, the implementation buggy
Paolo Bonzini writes:
> On 29/10/20 14:38, Markus Armbruster wrote:
>> In my opinion, the Linux-specific abstract UNIX domain socket feature
>> introduced in 5.1 should have been rejected. The feature is niche,
>> the interface clumsy, the implementation buggy and incomplete, and the
>> test cov
On Fri, Oct 30, 2020 at 02:10:26PM +0400, Marc-André Lureau wrote:
> On Fri, Oct 30, 2020 at 2:03 PM Marc-André Lureau <
> marcandre.lur...@gmail.com> wrote:
>
> >
> >
> > On Fri, Oct 30, 2020 at 2:17 AM Eduardo Habkost
> > wrote:
> >
> >> The array property registration code is hard to follow.
On Fri, Oct 30, 2020 at 11:11:19AM +0100, Markus Armbruster wrote:
> Marc-André Lureau writes:
>
> > Hi Markus,
> >
> > On Thu, Oct 29, 2020 at 5:43 PM Markus Armbruster wrote:
> >
> >> In my opinion, the Linux-specific abstract UNIX domain socket feature
> >> introduced in 5.1 should have been
In exynos4210_fimd_update(), the pointer s is dereferenced before
being check if it is valid, which may lead to NULL pointer dereference.
So move the assignment to global_width after checking that the s is valid
Reported-by: Euler Robot
Signed-off-by: Alex Chen
---
hw/display/exynos4210_fimd.c
In omap_lcd_interrupts(), the pointer omap_lcd is dereferenced before
being check if it is valid, which may lead to NULL pointer dereference.
So move the assignment to surface after checking that the omap_lcd is valid.
Reported-by: Euler Robot
Signed-off-by: Alex Chen
---
hw/display/omap_lcdc.c
Ping!
Hi all,
The patche2 ~7 have been reviewed for some time.
Could someone please pick it up？
Thanks,
Chen Qun
> -Original Message-
> From: Chenqun (kuhn)
> Sent: Friday, October 23, 2020 2:12 PM
> To: qemu-devel@nongnu.org; qemu-triv...@nongnu.org
> Cc: Pannengyuan ; lviv...@redhat
On Tue, Oct 27, 2020 at 06:38:40PM +0100, Jean-Philippe Brucker wrote:
> On Fri, Oct 23, 2020 at 12:47:02PM -0400, Peter Xu wrote:
> > On Fri, Oct 23, 2020 at 09:48:58AM +0200, Jean-Philippe Brucker wrote:
> > > Arm CPUs and SMMU support 4k, 16k and 64k page sizes. I don't think 16k is
> > > used a
From: Jiaxun Yang
Our current code assumed the target page size is always 4k
when handling PageMask and VPN2, however, variable page size
was just added to mips target and that's no longer true.
Fixes: ee3863b9d414 ("target/mips: Support variable page size")
Signed-off-by: Jiaxun Yang
Signed-of
Loongson-3 CPU family include Loongson-3A R1/R2/R3/R4 and Loongson-3B
R1/R2. Loongson-3A R1 is the oldest and its ISA is the smallest, while
Loongson-3A R4 is the newest and its ISA is almost the superset of all
others. To reduce complexity, in QEMU we just define two CPU types:
1, "Loongson-3A100
MIPSR6 (not only MIPS32R6) processors support unaligned access in
hardware, so set MO_UNALN in their default_tcg_memop_mask. Btw, new
Loongson-3 (such as Loongson-3A4000) also support unaligned access,
since both old and new Loongson-3 use the same binaries, we can simply
set MO_UNALN for all Loong
John Snow writes:
> On 10/29/20 3:55 PM, Thomas Huth wrote:
>> On 29/10/2020 18.12, John Snow wrote:
>>> On 10/29/20 12:49 PM, Alistair Francis wrote:
On Thu, Oct 29, 2020 at 9:41 AM Cornelia Huck wrote:
>
> On Thu, 29 Oct 2020 12:01:27 -0400
> John Snow wrote:
>
>> I
On Thu, Oct 08, 2020 at 03:22:14PM -0600, Alex Williamson wrote:
> On Thu, 8 Oct 2020 19:15:58 +0200
> Jean-Philippe Brucker wrote:
>
> > IOMMUs may declare memory regions spanning from 0 to UINT64_MAX. When
> > attempting to deal with such region, vfio_listener_region_del() passes a
> > size of
Implement fw_cfg_arch_key_name(), which returns the name of a
mips-specific key.
Reviewed-by: Philippe Mathieu-Daudé
Signed-off-by: Huacai Chen
Co-developed-by: Jiaxun Yang
Signed-off-by: Jiaxun Yang
---
hw/mips/fw_cfg.c| 35 +++
hw/mips/fw_cfg.h| 19 ++
On Thu, Oct 08, 2020 at 03:22:54PM -0600, Alex Williamson wrote:
> On Thu, 8 Oct 2020 19:15:56 +0200
> Jean-Philippe Brucker wrote:
>
> > From: Bharat Bhushan
> >
> > Set IOMMU supported page size mask same as host Linux supported page
> > size mask.
> >
> > Signed-off-by: Bharat Bhushan
> >
Update MIPS machine documentation to add Loongson-3 based machine description.
Signed-off-by: Huacai Chen
---
docs/system/target-mips.rst | 10 ++
1 file changed, 10 insertions(+)
diff --git a/docs/system/target-mips.rst b/docs/system/target-mips.rst
index cd2a931..138441b 100644
--- a/
Add Loongson-3 based machine support, it use liointc as the interrupt
controler and use GPEX as the pci controller. Currently it can work with
both TCG and KVM.
As the machine model is not based on any exiting physical hardware, the
name of the machine is "loongson3-virt". It may be superseded in
On Thu, Oct 08, 2020 at 07:15:48PM +0200, Jean-Philippe Brucker wrote:
> This series adds support for VFIO endpoints to virtio-iommu.
>
> Versions 1 to 9 were posted by Bharat Bhushan, but I am taking over for
> now since he doesn't have much time to spend on it. Thanks again Bharat
> for the work
Preparing to add Loongson-3 machine support, add Loongson-3's LEFI (a
UEFI-like interface for BIOS-Kernel boot parameters) helpers first.
Reviewed-by: Philippe Mathieu-Daudé
Signed-off-by: Huacai Chen
Co-developed-by: Jiaxun Yang
Signed-off-by: Jiaxun Yang
---
hw/mips/loongson3_bootp.c | 165
Kevin Wolf writes:
> Am 29.10.2020 um 15:02 hat Daniel P. Berrangé geschrieben:
>> On Wed, Oct 28, 2020 at 01:41:06PM +0100, Markus Armbruster wrote:
[...]
>> > Issue#1: our interface is differently ugly, for no good reason
>> >
>> > Like the Linux kernel, we also appropriate existing @path for
On Thu, 29 Oct 2020 17:36:14 +0100
Markus Armbruster wrote:
> Nothing major, looks almost ready to me.
>
> Lukas Straub writes:
>
> > The yank feature allows to recover from hanging qemu by "yanking"
> > at various parts. Other qemu systems can register themselves and
> > multiple yank functio
There will be a birds-of-a-feather session at KVM Forum,
a chance for us to get together and discuss about QEMU
continuous integration.
These sessions are a good opportunity to reach agreement
on topics that are hard to discuss via mailing lists.
Please add your suggestions to the agenda:
https:/
On Fri, Oct 30, 2020 at 06:27:35AM -0400, Michael S. Tsirkin wrote:
> On Thu, Oct 08, 2020 at 07:15:48PM +0200, Jean-Philippe Brucker wrote:
> > This series adds support for VFIO endpoints to virtio-iommu.
> >
> > Versions 1 to 9 were posted by Bharat Bhushan, but I am taking over for
> > now sinc
On Mon, Oct 19, 2020 at 12:43:29PM +0200, Eugenio Pérez wrote:
> This way we can tell between regular IOMMUTLBEntry (entry of IOMMU
> hardware) and notifications.
>
> In the notifications, we set explicitly if it is a MAPs or an UNMAP,
> instead of trusting in entry permissions to differentiate th
On Fri, 2020-10-30 at 05:01 -0400, Michael S. Tsirkin wrote:
> On Wed, Sep 30, 2020 at 10:32:42AM +0530, P J P wrote:
> >
> > [+Paolo, +Fam Zheng - for scsi]
> >
> > +-- On Mon, 28 Sep 2020, P J P wrote --+
> > > +-- On Wed, 16 Sep 2020, Peter Maydell wrote --+
> > > > On Wed, 16 Sep 2020 at 07:2
On Fri, 30 Oct 2020 at 10:10, Daniel P. Berrangé wrote:
> This
> makes it more appealing to leave existing bugs in the LP tracker until
> they are resolved, auto-closed, or there is a compelling reason to move
> to gitlab.
The compelling reason is that there is no way that I want to
have to consu
On Fri, Oct 30, 2020 at 9:46 AM Jason Wang wrote:
> On 2020/10/30 下午2:21, Stefan Hajnoczi wrote:
> > On Fri, Oct 30, 2020 at 3:04 AM Alex Williamson
> > wrote:
> >> It's great to revisit ideas, but proclaiming a uAPI is bad solely
> >> because the data transfer is opaque, without defining why tha
On Fri, Oct 30, 2020 at 12:00:33PM +0400, Marc-André Lureau wrote:
> On Fri, Oct 30, 2020 at 2:16 AM Eduardo Habkost wrote:
>
> > Make the code more generic and not specific to TYPE_DEVICE.
> >
> > Signed-off-by: Eduardo Habkost
> >
>
> What about dropping _qdev from the function name too?
I h
On Fri, Oct 30, 2020 at 02:03:07PM +0400, Marc-André Lureau wrote:
> On Fri, Oct 30, 2020 at 2:17 AM Eduardo Habkost wrote:
>
> > The array property registration code is hard to follow. Move the
> > two steps into separate functions that have clear
> > responsibilities.
> >
> > Signed-off-by: Ed
On Fri, 30 Oct 2020 09:19:46 +0100
Christian Schoenebeck wrote:
> Use mkdtemp() to generate a unique directory for the 9p 'local' tests.
>
> This fixes occasional 9p test failures when running 'make check -jN' if
> QEMU was compiled for multiple target architectures, because the individual
> arc
On Fri, Oct 30, 2020 at 11:29:25AM +0400, Marc-André Lureau wrote:
> On Fri, Oct 30, 2020 at 2:07 AM Eduardo Habkost wrote:
>
> > Make the code more generic and not specific to TYPE_DEVICE.
> >
> > Signed-off-by: Eduardo Habkost
> >
>
> Nice cleanup!, but fails to build atm
>
> ../hw/block/xen
On Fri, Oct 30, 2020 at 2:09 AM Eduardo Habkost wrote:
> Reuse function instead of calling object_property_add() directly.
> We need to hack ObjectProperty.release to make sure we will free
> the array property.
>
> Signed-off-by: Eduardo Habkost
>
that seems to be right, but could use more eye
On Fri, 30 Oct 2020 09:19:46 +0100
Christian Schoenebeck wrote:
> Coverity wants the return value of mkdir() to be checked, so let's
> pretend to do that. We're actually just making a dummy check and
> ignore the result, because we actually only care if the required
> directory exists and we have
On Thu, Oct 29, 2020 at 10:02:37AM +0100, Philippe Mathieu-Daudé wrote:
> On 10/28/20 7:24 PM, Philippe Mathieu-Daudé wrote:
> > On 10/28/20 4:16 PM, Stefan Hajnoczi wrote:
> >> On Tue, Oct 27, 2020 at 02:55:35PM +0100, Philippe Mathieu-Daudé wrote:
> >>> Rename Submission Queue flags with 'Sq' a
On Thu, 29 Oct 2020 at 20:28, Peter Xu wrote:
>
> On Thu, Oct 29, 2020 at 07:34:33PM +, Dr. David Alan Gilbert wrote:
> > > Here's qemu process 3514:
> > > Thread 5 (Thread 0x3ff4affd910 (LWP 3628)):
> > > #0 0x03ff94c8d936 in futex_wait_cancelable (private= > > out>, expected=0, futex_wo
On Tue, 27 Oct 2020 at 14:17, David Gibson wrote:
>
> The following changes since commit d55450df995d6223486db11c66491cbf6c131523:
>
> Merge remote-tracking branch
> 'remotes/dgilbert/tags/pull-migration-20201026a' into staging (2020-10-27
> 10:25:42 +)
>
> are available in the Git reposit
On Freitag, 30. Oktober 2020 12:44:18 CET Greg Kurz wrote:
> On Fri, 30 Oct 2020 09:19:46 +0100
>
> Christian Schoenebeck wrote:
> > Coverity wants the return value of mkdir() to be checked, so let's
> > pretend to do that. We're actually just making a dummy check and
> > ignore the result, becau
On Fri, Oct 30, 2020 at 08:04:54AM +, Tian, Kevin wrote:
> > From: Stefan Hajnoczi
> > Sent: Friday, October 30, 2020 3:51 PM
> >
> > Hi,
> > The "Scalable Work Submission in Device Virtualization" talk at KVM
> > Forum 2020 was interesting and I have some beginner questions about
> > ENQCMD:
On 2020/10/30 下午7:13, Stefan Hajnoczi wrote:
On Fri, Oct 30, 2020 at 9:46 AM Jason Wang wrote:
On 2020/10/30 下午2:21, Stefan Hajnoczi wrote:
On Fri, Oct 30, 2020 at 3:04 AM Alex Williamson
wrote:
It's great to revisit ideas, but proclaiming a uAPI is bad solely
because the data transfer is
On Fri, 30 Oct 2020 at 12:02, Christian Schoenebeck
wrote:
> On Freitag, 30. Oktober 2020 12:44:18 CET Greg Kurz wrote:
> It's not clear to me where this coverity report is accessible online. A quick
> search only brought me to statistics about its latest check, but not the
> details of the report
From: "Jason J. Herne"
The architecture states that the iplb location is only written to low
core for list directed ipl and not for traditional ccw ipl. If we don't
skip this then operating systems that load by reading into low core
memory may fail to start.
We should also not write the iplb poi
On Fri, 30 Oct 2020 12:59:48 +0100
Christian Schoenebeck wrote:
> On Freitag, 30. Oktober 2020 12:44:18 CET Greg Kurz wrote:
> > On Fri, 30 Oct 2020 09:19:46 +0100
> >
> > Christian Schoenebeck wrote:
> > > Coverity wants the return value of mkdir() to be checked, so let's
> > > pretend to do t
1 - 100 of 312 matches
Mail list logo
