Currently, when a notifier is attempted to be registered and its
flags are not supported (especially the MAP one) by the IOMMU MR,
we generally abruptly exit in the IOMMU code. The failure could be
handled more nicely in the caller and especially in the VFIO code.
So let's allow memory_region_regi
The container error integer field is currently used to store
the first error potentially encountered during any
vfio_listener_region_add() call. However this fails to propagate
detailed error messages up to the vfio_connect_container caller.
Instead of using an integer, let's use an Error handle.
This series allows the memory_region_register_iommu_notifier()
to fail. As of now, when a MAP notifier is attempted to be
registered along with SMMUv3 or AMD IOMMU, we exit in the IOMMU
MR notify_flag_changed() callback.
In case of VFIO assigned device hotplug, this could be handled
more nicely di
Drop the duplicated definition of cpuid AVX512_VBMI marco and rename it
as CPUID_7_0_ECX_AVX512_VBMI.
Signed-off-by: Tao Xu
---
target/i386/cpu.c | 4 ++--
target/i386/cpu.h | 3 +--
target/i386/hvf/x86_cpuid.c | 2 +-
3 files changed, 4 insertions(+), 5 deletions(-)
diff --
Add some comments, clean up comments over 80 chars per line. And there
is an extra line in comment of CPUID_8000_0008_EBX_WBNOINVD, remove
the extra enter and spaces.
Signed-off-by: Tao Xu
---
target/i386/cpu.h | 164 ++
1 file changed, 107 insertions(
Add some comments, clean up comments over 80 chars per line. And there
is an extra line in comment of CPUID_8000_0008_EBX_WBNOINVD, remove
the extra enter and spaces.
Drop the duplicated definition of cpuid AVX512_VBMI marco and rename it
as CPUID_7_0_ECX_AVX512_VBMI.
Changelog:
v3:
- split t
> From: Kevin Wolf [mailto:kw...@redhat.com]
> Am 20.09.2019 um 09:25 hat Pavel Dovgalyuk geschrieben:
> > > From: Kevin Wolf [mailto:kw...@redhat.com]
> > > Am 19.09.2019 um 14:10 hat Pavel Dovgalyuk geschrieben:
> > > > > From: Kevin Wolf [mailto:kw...@redhat.com]
> > > > > diff --git a/block/blo
On Fri, Sep 20, 2019 at 07:53:51PM +0100, Dr. David Alan Gilbert wrote:
>* Wei Yang (richardw.y...@linux.intel.com) wrote:
>> Hi, Dave and Juan
>>
>> Would you mind taking a look at this one?
>
>Yes, I'll have a look, I'm just fighting through a bunch of other stuff.
>
Yep, thanks ~ Me too :-)
H
QEMU stores current BAR assignments in 2 places - in the raw config space
array and io_regions structs. Once set, the config space array remembers
these but BARs in io_regions are reset/restored every time the device is
disabled/enabled, i.e. when MMIO bit in the command register is flipped.
A sPA
On 19/09/2019 23:39, miny...@acm.org wrote:
> From: Corey Minyard
>
> Using the UUID that qemu generates probably isn't the best thing
> to do, allow it to be passed in via properties, and use QemuUUID
> for the type.
>
> If the UUID is not set, return an unsupported command error. This
> way w
On 19/09/2019 23:39, miny...@acm.org wrote:
> From: Corey Minyard
>
> This is for IPMI, which will behave differently if the UUID is
> not set.
>
> Signed-off-by: Corey Minyard
> Cc: Fam Zheng
> Cc: Michael S. Tsirkin
> Cc: Marc-André Lureau
Reviewed-by: Cédric Le Goater
C.
> ---
> inc
On 21/09/2019 06:37, Joel Stanley wrote:
> On Fri, 20 Sep 2019 at 15:15, Cédric Le Goater wrote:
>>
>> On 20/09/2019 06:10, Andrew Jeffery wrote:
>>>
>>>
>>> On Thu, 19 Sep 2019, at 15:19, Cédric Le Goater wrote:
From: Joel Stanley
The SCU controller on the AST2600 SoC has extra re
On 19/09/2019 23:39, miny...@acm.org wrote:
> From: Corey Minyard
>
> Add the watchdog pretimeout to the bits that cause an interrupt on attn.
> Otherwise the user won't know.
>
> Signed-off-by: Corey Minyard
Reviewed-by: Cédric Le Goater
C.
> ---
> hw/ipmi/ipmi_bmc_sim.c | 4 +++-
> 1 fil
On 9/21/2019 2:33 AM, Eduardo Habkost wrote:
On Fri, Sep 20, 2019 at 01:31:36PM +0800, Tao Xu wrote:
Drop the duplicate definition of CPUID_7_0_ECX_VBMI. And add some
comments, clean up comments over 80 chars per line.
There is an extra line in comment of CPUID_8000_0008_EBX_WBNOINVD,
remove th
On Fri, Sep 20, 2019 at 03:58:51PM +0200, Igor Mammedov wrote:
> On Fri, 20 Sep 2019 20:19:51 +0800
> Peter Xu wrote:
>
> > On Fri, Sep 20, 2019 at 12:21:20PM +0200, Paolo Bonzini wrote:
> > > A single ram_addr (representing a host-virtual address) could be aliased
> > > to multiple guest physica
Public bug reported:
I use macOS with own built Qemu to run old XP system that I have migrated from
physical machine. My setup is very simple qemu-system-x86_64 with args:
-machine pc,accel=hvf,usb=off,vmport=off
-cpu host
-vga std
-m 2048
-drive file="$img",format=qcow2,cache=none,detect-zeroes=
On 20.09.2019 20:55, John Snow wrote:
>
> On 9/18/19 12:29 PM, Denis Plotnikov wrote:
>> On 12.09.2019 11:46, Denis Plotnikov wrote:
>>> ping!
>>>
> https://lists.gnu.org/archive/html/qemu-devel/2019-09/msg00943.html
>
> I was under the impression you were addressing feedback from Vladimir.
>
> --j
On Fri, Sep 06, 2019 at 07:12:18PM +, Moger, Babu wrote:
> Introduce cpu core complex id(ccx_id) in x86CPU topology.
> Each CCX can have upto 4 cores and share same L3 cache.
> This information is required to build the topology in
> new apyc mode.
>
> Signed-off-by: Babu Moger
> ---
> hw/cor
On Fri, 2019-09-20 at 17:14 -0400, John Snow wrote:
>
> On 9/12/19 6:30 PM, Maxim Levitsky wrote:
> > This patch series is continuation of my work to add encryption
> > key managment to luks/qcow2 with luks.
> >
> > This is second version of this patch set.
> > The changes are mostly addressing t
19 matches
Mail list logo
