On Wed, 27 Mar 2019 11:56:10 +1100
David Gibson wrote:
> On Tue, Mar 26, 2019 at 08:09:53AM +0100, Greg Kurz wrote:
> > On Tue, 26 Mar 2019 10:47:15 +1100
> > David Gibson wrote:
> >
> > > On Mon, Mar 25, 2019 at 05:33:21PM +0100, Greg Kurz wrote:
> > > > On Mon, 25 Mar 2019 11:53:47 +1100
On Mon, Mar 25, 2019 at 07:42:27PM -0500, Corey Minyard wrote:
> On Sun, Mar 24, 2019 at 07:05:23PM +0100, Ernest Esene wrote:
> > Categorize devices in "uncategorised devices" section
> > This patch is based on BiteSizedTask.
> >
> > Signed-off-by: Ernest Esene
>
> I'm not 100% sure the use of
On Wed, 2019-03-27 at 14:41 +0800, Peter Xu wrote:
> On Tue, Mar 26, 2019 at 01:23:12PM +, Elijah Shakkour wrote:
> > Adding QEMU-devel
>
> Hi, Elijah,
>
> >
> > -Original Message-
> > From: Michael S. Tsirkin
> > Sent: Tuesday, March 26, 2019 2:53 PM
> > To: Elijah Shakkour
> > C
On 27.03.19 01:12, David Gibson wrote:
> On Tue, Mar 26, 2019 at 06:02:51PM +0100, David Hildenbrand wrote:
>> On 26.03.19 15:08, Igor Mammedov wrote:
>>> On Tue, 26 Mar 2019 14:50:58 +1100
>>> David Gibson wrote:
>>>
qemu_getrampagesize() works out the minimum host page size backing any of
>
On Tue, Mar 26, 2019 at 03:49:04PM -0300, Eduardo Habkost wrote:
> On Tue, Mar 26, 2019 at 07:43:51PM +0100, Hervé Poussineau wrote:
> > Le 24/03/2019 à 19:05, Ernest Esene a écrit :
> > > Categorize devices in "uncategorised devices" section
> > > This patch is based on BiteSizedTask.
> > >
> > >
On Wed, Mar 27, 2019 at 08:57:56AM +0100, Knut Omang wrote:
> On Wed, 2019-03-27 at 14:41 +0800, Peter Xu wrote:
> > On Tue, Mar 26, 2019 at 01:23:12PM +, Elijah Shakkour wrote:
> > > Adding QEMU-devel
> >
> > Hi, Elijah,
> >
> > >
> > > -Original Message-
> > > From: Michael S. Tsir
On Wed, 27 Mar 2019 11:11:46 +1100
David Gibson wrote:
> On Tue, Mar 26, 2019 at 03:08:20PM +0100, Igor Mammedov wrote:
> > On Tue, 26 Mar 2019 14:50:58 +1100
> > David Gibson wrote:
> >
> > > qemu_getrampagesize() works out the minimum host page size backing any of
> > > guest RAM. This is
On 27/03/2019 00:05, Alex Williamson wrote:
If we try to use the intel-iommu device with vfio-pci devices without
caching mode enabled, we're told:
qemu-system-x86_64: We need to set caching-mode=1 for intel-iommu to enable
device assignment with IOMMU protection.
But to enable caching mo
Patchew URL:
https://patchew.org/QEMU/1553592437-109191-1-git-send-email-k...@andestech.com/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Message-id: 1553592437-109191-1-git-send-email-k...@andestech.com
Subject: [Qemu-devel] [PATCH] target/
On Wed, Mar 27, 2019 at 08:09:26AM +0100, Greg Kurz wrote:
> On Wed, 27 Mar 2019 11:56:10 +1100
> David Gibson wrote:
>
> > On Tue, Mar 26, 2019 at 08:09:53AM +0100, Greg Kurz wrote:
> > > On Tue, 26 Mar 2019 10:47:15 +1100
> > > David Gibson wrote:
> > >
> > > > On Mon, Mar 25, 2019 at 05:33
On Wed, Mar 27, 2019 at 09:10:01AM +0100, David Hildenbrand wrote:
> On 27.03.19 01:12, David Gibson wrote:
> > On Tue, Mar 26, 2019 at 06:02:51PM +0100, David Hildenbrand wrote:
> >> On 26.03.19 15:08, Igor Mammedov wrote:
> >>> On Tue, 26 Mar 2019 14:50:58 +1100
> >>> David Gibson wrote:
> >>>
>
On Wed, 27 Mar 2019 09:10:01 +0100
David Hildenbrand wrote:
> On 27.03.19 01:12, David Gibson wrote:
> > On Tue, Mar 26, 2019 at 06:02:51PM +0100, David Hildenbrand wrote:
> >> On 26.03.19 15:08, Igor Mammedov wrote:
> >>> On Tue, 26 Mar 2019 14:50:58 +1100
> >>> David Gibson wrote:
> >>>
Le mer. 27 mars 2019 00:06, Alex Williamson a
écrit :
> If we try to use the intel-iommu device with vfio-pci devices without
> caching mode enabled, we're told:
>
> qemu-system-x86_64: We need to set caching-mode=1 for intel-iommu to
> enable
> device assignment with IOMMU protection.
>
> Bu
On Wed, Mar 27, 2019 at 09:57:45AM +0100, Igor Mammedov wrote:
> On Wed, 27 Mar 2019 11:11:46 +1100
> David Gibson wrote:
>
> > On Tue, Mar 26, 2019 at 03:08:20PM +0100, Igor Mammedov wrote:
> > > On Tue, 26 Mar 2019 14:50:58 +1100
> > > David Gibson wrote:
> > >
> > > > qemu_getrampagesize()
iotest 235 currently only works with KVM - this is bad for systems where
it is not available, e.g. CI pipelines. The test also works when using
"tcg" as accelerator, so we can simply add that to the list of accelerators,
too.
Signed-off-by: Thomas Huth
---
v2: Do not remove the test from the "qu
Le mer. 27 mars 2019 10:24, Thomas Huth a écrit :
> iotest 235 currently only works with KVM - this is bad for systems where
> it is not available, e.g. CI pipelines. The test also works when using
> "tcg" as accelerator, so we can simply add that to the list of
> accelerators,
> too.
>
> Signed-
On Wed, 27 Mar 2019 20:07:57 +1100
David Gibson wrote:
> On Wed, Mar 27, 2019 at 09:57:45AM +0100, Igor Mammedov wrote:
> > On Wed, 27 Mar 2019 11:11:46 +1100
> > David Gibson wrote:
> >
> > > On Tue, Mar 26, 2019 at 03:08:20PM +0100, Igor Mammedov wrote:
> > > > On Tue, 26 Mar 2019 14:50:5
Hi Yang, Xiao,
Just adding few things, because I'm currently exploring the QEMU modules
in order to reduce the boot time and the footprint.
On Tue, Mar 26, 2019 at 09:27:09AM +, Stefan Hajnoczi wrote:
> On Tue, Mar 26, 2019 at 03:00:05PM +0800, Xiao Guangrong wrote:
> > On 3/26/19 7:18 AM, Pao
On Wed, 27 Mar 2019 19:38:27 +1100
David Gibson wrote:
> On Wed, Mar 27, 2019 at 08:09:26AM +0100, Greg Kurz wrote:
> > On Wed, 27 Mar 2019 11:56:10 +1100
> > David Gibson wrote:
> >
> > > On Tue, Mar 26, 2019 at 08:09:53AM +0100, Greg Kurz wrote:
> > > > On Tue, 26 Mar 2019 10:47:15 +1100
On 25/03/2019 - 15:52:27, Daniel P. Berrange wrote:
> On Mon, Mar 25, 2019 at 04:25:19PM +0100, Marc-André Lureau wrote:
> > Hi
> >
> > On Mon, Mar 25, 2019 at 3:07 PM Daniel P. Berrangé
> > wrote:
> > >
> > > Most of the seccomp functions return errnos as a negative return
> > > value. The code
IEC binary prefixes are already defined in "qemu/units.h",
so we can remove redundant definitions in "block/vhdx.h".
Signed-off-by: Stefano Garzarella
---
block/vhdx.c | 3 ++-
block/vhdx.h | 6 +-
2 files changed, 3 insertions(+), 6 deletions(-)
diff --git a/block/vhdx.c b/block/vhdx.c
ind
v2:
- Included units.h directly in the vhdx.h header file (John, Philippe)
- Added a comment next to DEFAULT_LOG_SIZE definition (Kevin)
- Added a second patch where I fixed some size constants using IEC
binary prefixes.
Note: checkpatch is not happy about a change in vhdx.h but all the comment
Using IEC binary prefixes in order to make the code more readable,
with the exception of DEFAULT_LOG_SIZE because it's passed to
stringify().
Signed-off-by: Stefano Garzarella
---
block/vhdx-log.c | 2 +-
block/vhdx.c | 4 ++--
block/vhdx.h | 10 ++
3 files changed, 9 insertion
The following changes since commit 49fc899f8d673dd9e73f3db0d9e9ea60b77c331b:
Update version for v4.0.0-rc1 release (2019-03-26 17:02:29 +)
are available in the Git repository at:
https://github.com/otubo/qemu.git tags/pull-seccomp-20190327
for you to fetch changes up to
From: Daniel P. Berrangé
The Mesa library tries to set process affinity on some of its threads in
order to optimize its performance. Currently this results in QEMU being
immediately terminated when seccomp is enabled.
Mesa doesn't consider failure of the process affinity settings to be
fatal to
On Tue, 26 Mar 2019 16:30:50 +0100
Laszlo Ersek wrote:
> On 03/26/19 15:19, Laszlo Ersek wrote:
> > On 03/26/19 14:09, Igor Mammedov wrote:
> >> once FW provides a pointer to SMBIOS entry point like it does for
> >> RSDP it should be possible to enable this one the same way.
> >>
> >> Signed-of
From: Daniel P. Berrangé
Most of the seccomp functions return errnos as a negative return
value. The code is currently ignoring these and reporting a generic
error message for all seccomp failure scenarios making debugging
painful. Report a more precise error from each failed call and include
err
On Wed, Mar 27, 2019 at 10:59:03AM +0100, Eduardo Otubo wrote:
> From: Daniel P. Berrangé
>
> The Mesa library tries to set process affinity on some of its threads in
> order to optimize its performance. Currently this results in QEMU being
> immediately terminated when seccomp is enabled.
>
> M
Thanks,
Also please notice that the mentioned commit in the commit message has it’s
commit id changed to b69864e.
Sam
> On 27 Mar 2019, at 2:35, Eric Blake wrote:
>
> On 3/26/19 2:58 PM, Sam Eiderman wrote:
>> Commit fb2105b ("vmdk: Support version=3 in VMDK descriptor files") fixed
>> the pr
On Tue, 26 Mar 2019 15:16:57 +0100
Laszlo Ersek wrote:
> On 03/26/19 14:09, Igor Mammedov wrote:
> > For testcase to use UEFI firmware, one needs to provide and specify
> > firmwarei and varstore blobs names in test_data { uefi_fl1, uefi_fl2) }
> > fields respectively and RAM start address plus s
Public bug reported:
UEFI helper app exposes the pointer to RSDP ACPI table that firmware allocates
in guest's RAM
but it doesn't do so for SMBIOS tables. Hence bios table test would skip
testing SMBIOS tables
to workaround shortcoming. This bug is a request to expose two new entry point
fields
Remove a space before bracket to fix checkpatch error
"ERROR: space prohibited between function name and open parenthesis".
Signed-off-by: Jules Irenge
---
target/mips/cp0_timer.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/mips/cp0_timer.c b/target/mips/cp0_timer
Remove a space before bracket to fix checkpatch error
"ERROR: do not initialise statics to 0 or NULL".
Signed-off-by: Jules Irenge
---
target/mips/cp0_timer.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/mips/cp0_timer.c b/target/mips/cp0_timer.c
index 96a8cb68ef..
On Wed, 20 Mar 2019 17:46:09 PDT (-0700), Alistair Francis wrote:
The irq is incorrectly calculated to be off by one. It has worked in the
past as the priority_base offset has also been set incorrectly. We are
about to fix the priority_base offset so first first the irq
calculation.
Signed-off-b
Hi,
On 3/27/19 12:05 AM, Alex Williamson wrote:
> If we try to use the intel-iommu device with vfio-pci devices without
> caching mode enabled, we're told:
>
> qemu-system-x86_64: We need to set caching-mode=1 for intel-iommu to enable
> device assignment with IOMMU protection.
>
> But to en
Add /* comment to fix checkpatch warning
"WARNING: Block comments use a leading /* on a separate line".
Signed-off-by: Jules Irenge
---
target/mips/cp0_timer.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/target/mips/cp0_timer.c b/target/mips/cp0_timer.c
index ffa460b
On 3/21/19 9:55 AM, Nir Weiner wrote:
Originally migration was not possible with vhost-scsi because
as part of migration, the source host target SCSI device state
needs to be saved and loaded into the destination host target SCSI
device. This cannot be done by QEMU.
As this can be handled eithe
Launchpad has imported 1 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1578278.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://hel
On 13/03/2019 17.31, Jason J. Herne wrote:
> Add verbose error output for when unexpected i/o errors happen. This eases the
> burden of debugging and reporting i/o errors. No error information is printed
> in the success case, here is an example of what is output on error:
>
> cio device error
>
On Tue, Mar 26, 2019 at 06:48:54PM +0100, Markus Armbruster wrote:
> Known dependencies:
>
> * migration object_init() must run before configure_blockdev(), so block
> backends can register migration blockers
>
> * configure_blockdev() must run before machine_set_property(), so
> machine prop
On 03/27/19 11:09, Igor Mammedov wrote:
> On Tue, 26 Mar 2019 15:16:57 +0100
> Laszlo Ersek wrote:
>
>> On 03/26/19 14:09, Igor Mammedov wrote:
>>> For testcase to use UEFI firmware, one needs to provide and specify
>>> firmwarei and varstore blobs names in test_data { uefi_fl1, uefi_fl2) }
>>> f
On 20/03/2019 16.11, Jason J. Herne wrote:
> On 3/13/19 12:31 PM, Jason J. Herne wrote:
>> This is to support booting from vfio-ccw dasd devices. We basically
>> implement
>> the real hardware ipl procedure. This allows for booting Linux guests on
>> vfio-ccw devices.
>>
>> vfio-ccw's channel progr
Discussion on qemu-devel:
[Qemu-devel] [PATCH for 4.1 v2 09/13] tests: acpi: ignore SMBIOS tests when
UEFI firmware is used
1553605799-168605-10-git-send-email-imammedo@redhat.com">http://mid.mail-archive.com/1553605799-168605-10-git-send-email-imammedo@redhat.com
https://lists.gnu.org/archive/htm
On 3/26/19 5:47 PM, Dongli Zhang wrote:
I am reporting an error that the scsi lun cannot initialize successfully when I
am emulating megasas scsi controller with qemu.
I am not sure if this is issue in qemu or linux kernel.
When 'lun=1' is specified, there is "Unexpected response from lun 1 whi
Hi everyone,
I’m sending this email to present myself and a project that I’m planning to
submit to QEMU/GSoC this year. As I see that this project could result in
useful improvements and tools to the community, I would love to have
feedback from the community and perhaps make it even more useful.
On Wed, 27 Mar 2019 at 01:09, Chen Zhang wrote:
> Just double-checked on a MacMini mid 2011 with macOS 10.13.6, Xcode 10.1.
> This NSWindow API did exist, and the patch could be built without error.
> Searching convertPointFromScreen in Xcode.app’s platform SDK showed that it
> was defined at li
otubo/qemu.git tags/pull-seccomp-20190327
>
> for you to fetch changes up to 9d6951a9463e0fb8d39cc546f9c37756aed5b19d:
>
> seccomp: report more useful errors from seccomp (2019-03-27 10:55:13 +0100)
>
> --
Thanks a lot!
пт, 22 мар. 2019 г. в 16:15, Greg Kurz :
> On Fri, 22 Mar 2019 11:57:04 +0200
> "П, Алексей" wrote:
>
> > Hi there. Cannot find any info and examples about "proxy" and "handle"
> > types of fsdriver of virtfs. Can anyone advise me description of?
> > Witrh regards/
>
> Hi,
>
> The
Hi Alex,
On 3/26/19 11:55 PM, Alex Williamson wrote:
> Conventional PCI buses pre-date requester IDs. An IOMMU cannot
> distinguish by devfn & bus between devices in a conventional PCI
> topology and therefore we cannot assign them separate AddressSpaces.
> By taking this requester ID aliasing in
hvf_handle_io needs the poisoned type CPUArchState as its argument.
Declaring it if NEED_CPU_H is defined enables include/sysemu/hvf.h
to be included for common object compilation as well.
Cc: Roman Bolshakov
Cc: Paolo Bonzini
Signed-off-by: Sukrit Bhatnagar
---
include/sysemu/hvf.h | 4
Keep the calls made to synchronize cpu by all hypervisors in one place
inside cpu_synchronize_* functions in include/sysemu/hw_accel.h
Cc: Richard Henderson
Cc: Paolo Bonzini
Signed-off-by: Sukrit Bhatnagar
---
cpus.c| 12
include/sysemu/hw_accel.h | 10 +++
Changes made in v2:
- added a patch to declare hvf_handle_io only if NEED_CPU_H
is defined so that the poisoned type CPUArchState does not
produce an error when include/sysemu/hvf.h is included for
common object compilation
Link to v1:
https://lists.gnu.org/archive/html/qemu-devel/2019-03/ms
On Wed, Mar 27, 2019 at 10:44:03AM +0100, Greg Kurz wrote:
> On Wed, 27 Mar 2019 19:38:27 +1100
> David Gibson wrote:
>
> > On Wed, Mar 27, 2019 at 08:09:26AM +0100, Greg Kurz wrote:
> > > On Wed, 27 Mar 2019 11:56:10 +1100
> > > David Gibson wrote:
> > >
> > > > On Tue, Mar 26, 2019 at 08:09
So I'm trying to add IPv6 support to hostfwd, as requested in
https://bugs.launchpad.net/qemu/+bug/1724590
I'm not entirely sure what would be the right parameter format in case of
IPv6 support.
Current IPv4-only format is
"hostfwd=[tcp|udp]:[hostaddr]:hostport-[guestaddr]:guestport", example
usa
On Wed, Mar 27, 2019 at 10:38:38AM +0100, Igor Mammedov wrote:
> On Wed, 27 Mar 2019 20:07:57 +1100
> David Gibson wrote:
>
> > On Wed, Mar 27, 2019 at 09:57:45AM +0100, Igor Mammedov wrote:
> > > On Wed, 27 Mar 2019 11:11:46 +1100
> > > David Gibson wrote:
> > >
> > > > On Tue, Mar 26, 2019
> From: Jules Irenge
> Subject: [PATCH] target: mips: remove a space before open parenthesis to fix
> checkpatch error
>
> Remove a space before bracket to fix checkpatch error
> "ERROR: space prohibited between function name and open parenthesis".
>
> Signed-off-by: Jules Irenge
> ---
> tar
On 13/03/2019 17.31, Jason J. Herne wrote:
> Create a separate library for channel i/o related code. This decouples
> channel i/o operations from virtio and allows us to make use of them for
> the real dasd boot path.
>
> Signed-off-by: Jason J. Herne
> Reviewed-by: Cornelia Huck
> ---
Reviewed
From: Daniel P. Berrangé
The Mesa library tries to set process affinity on some of its threads in
order to optimize its performance. Currently this results in QEMU being
immediately terminated when seccomp is enabled.
Mesa doesn't consider failure of the process affinity settings to be
fatal to
The following changes since commit 49fc899f8d673dd9e73f3db0d9e9ea60b77c331b:
Update version for v4.0.0-rc1 release (2019-03-26 17:02:29 +)
are available in the Git repository at:
https://github.com/otubo/qemu.git tags/pull-seccomp-20190327
for you to fetch changes up to
From: Daniel P. Berrangé
Most of the seccomp functions return errnos as a negative return
value. The code is currently ignoring these and reporting a generic
error message for all seccomp failure scenarios making debugging
painful. Report a more precise error from each failed call and include
err
Vanderson Martins do Rosario writes:
> Hi everyone,
>
> I’m sending this email to present myself and a project that I’m planning to
> submit to QEMU/GSoC this year. As I see that this project could result in
> useful improvements and tools to the community, I would love to have
> feedback from
Set category and describe IPMI devices
Signed-off-by: Ernest Esene
---
v2:
* split into different patches
* change category and description for management controllers
---
hw/ipmi/ipmi_bmc_extern.c | 2 ++
hw/ipmi/ipmi_bmc_sim.c| 2 ++
hw/ipmi/isa_ipmi_bt.c | 2 ++
hw/ipmi/isa_ipmi_k
Set category and describe TPM device
Signed-off-by: Ernest Esene
---
v2:
* split into separate patch
---
hw/tpm/tpm_tis.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/hw/tpm/tpm_tis.c b/hw/tpm/tpm_tis.c
index fd183e8deb..368242 100644
--- a/hw/tpm/tpm_tis.c
+++ b/hw/tpm/tpm_tis.
Set category and describe DIMM devices
Signed-off-by: Ernest Esene
---
v2:
* split into separate patches
---
hw/mem/nvdimm.c | 1 +
hw/mem/pc-dimm.c | 1 +
2 files changed, 2 insertions(+)
diff --git a/hw/mem/nvdimm.c b/hw/mem/nvdimm.c
index bf2adf5e16..a334dbe1f5 100644
--- a/hw/mem/nvdimm
On 27/03/19 10:41, Stefano Garzarella wrote:
> I found that libgnutls, libspice-server and libnuma initialization takes
> most of the time. I disabled these libraries (--disable-numa --disable-gnutls
> --disable-spice) to understand the maximum speed up and I gained 10 ms
> during the boot:
> -
On Wed, 27 Mar 2019 23:06:42 +1100
David Gibson wrote:
> On Wed, Mar 27, 2019 at 10:44:03AM +0100, Greg Kurz wrote:
> > On Wed, 27 Mar 2019 19:38:27 +1100
> > David Gibson wrote:
> >
> > > On Wed, Mar 27, 2019 at 08:09:26AM +0100, Greg Kurz wrote:
> > > > On Wed, 27 Mar 2019 11:56:10 +1100
For devices that require msi_init/msix_init to succeed, add a
dependency on CONFIG_MSI_NONBROKEN. This will prevent those devices
from appearing in a binary that cannot instantiate them.
Signed-off-by: Paolo Bonzini
---
Kconfig.host | 3 +++
Makefile | 3 ++-
hw/Kconfig
From: Philippe Mathieu-Daudé
This fixes when configuring with --without-default-devices:
$ qemu-system-mips64 -bios /dev/null -M malta
qemu-system-mips64: Unknown device 'piix4-usb-uhci' for bus 'PCI'
Fixes: 7c28b925b7e
Signed-off-by: Philippe Mathieu-Daudé
Message-Id: <20190316200818.8265
The following changes since commit 9164add701788075f229b560bc3e92f6562ff857:
Merge remote-tracking branch 'remotes/stsquad/tags/pull-gitdm-next-120319-1'
into staging (2019-03-14 13:48:48 +)
are available in the git repository at:
git://github.com/bonzini/qemu.git tags/for-upstream
fo
From: Thomas Huth
For the downstream distribution of QEMU, we want to compile without
CONFIG_PARALLEL. Commit 9157eee1b1c076ff3 already moved the function
parallel_hds_isa_init() (which is still required for linking) into a file
that is included anyway, but commit bb3d5ea858e7f888563a moved it
to
Not all interrupt controllers have a working implementation of
message-signalled interrupts; in some cases, the guest may expect
MSI to work but it won't due to the buggy or lacking emulation.
In QEMU this is represented by the "msi_nonbroken" variable. This
patch adds a new configuration symbol
From: Philippe Mathieu-Daudé
This fixes when configuring with CONFIG_PCI_DEVICES=n:
$ qemu-system-ppc64 -bios /dev/null -M ppce500
qemu-system-ppc64: Unsupported NIC model: virtio-net-pci
And:
$ qemu-system-ppc64 -bios /dev/null -M mpc8544ds
qemu-system-ppc64: Unsupported NIC model: vi
From: Alistair Francis
Set msi_nonbroken as true for the PLIC.
According to the comment located here:
https://git.qemu.org/?p=qemu.git;a=blob;f=hw/pci/msi.c;h=47d2b0f33c664533b8dbd5cb17faa8e6a01afe1f;hb=HEAD#l38
the msi_nonbroken variable should be set to true even if they don't
support MSI. In
From: Philippe Mathieu-Daudé
This fixes when configuring with CONFIG_PCI_DEVICES=n:
$ qemu-system-x86_64 -M q35
qemu-system-x86_64: Unsupported NIC model: e1000e
$ qemu-system-x86_64 -M pc
qemu-system-x86_64: Unsupported NIC model: e1000
Fixes: 7c28b925b7e
Signed-off-by: Philippe Mathie
From: "Singh, Brijesh"
The RAM device presents a memory region that should be handled
as an IO region and should not be pinned.
In the case of the vfio-pci, RAM device represents a MMIO BAR
and the memory region is not backed by pages hence
KVM_MEMORY_ENCRYPT_REG_REGION fails to lock the memory
This removes the duplicated initialization code.
Reviewed-by: Dr. David Alan Gilbert
Signed-off-by: Paolo Bonzini
---
tests/Makefile.include | 3 --
tests/test-announce-self.c | 73 --
tests/virtio-net-test.c| 30 +++
3 files
From: "Singh, Brijesh"
Currently, a callback registered through the RAMBlock notifier
is not able to get the memory region type (i.e callback is not
able to use memory_region_is_ram_device function). This is
because mr->ram assignment happens _after_ the memory is allocated
whereas the callback i
From: Philippe Mathieu-Daudé
This fixes when configuring with CONFIG_PCI_DEVICES=n:
$ qemu-system-alpha
qemu-system-alpha: Unsupported NIC model: e1000
Fixes: d1a95ef4ac
Signed-off-by: Philippe Mathieu-Daudé
Message-Id: <20190316200818.8265-15-phi...@redhat.com>
Signed-off-by: Paolo Bonzini
It is only needed through I82378, which also selects it.
Reviewed-by: Stefano Garzarella
Signed-off-by: Paolo Bonzini
---
hw/ppc/Kconfig | 1 -
1 file changed, 1 deletion(-)
diff --git a/hw/ppc/Kconfig b/hw/ppc/Kconfig
index 73b473c..bbe5a64 100644
--- a/hw/ppc/Kconfig
+++ b/hw/ppc/Kconfig
@@
CONFIG_I82374 is not needed for PC machines, since they create
i8257 directly instead.
Reported-by: Miroslav Rezanina
Reviewed-by: Stefano Garzarella
Signed-off-by: Paolo Bonzini
---
hw/i386/Kconfig | 1 -
1 file changed, 1 deletion(-)
diff --git a/hw/i386/Kconfig b/hw/i386/Kconfig
index 4e44
From: Peter Xu
Previously we have per-device system memory aliases when DMAR is
disabled by the system. It will slow the system down if there are
lots of devices especially when DMAR is disabled, because each of the
aliased system address space will contain O(N) slots, and rendering
such N addre
Le mer. 27 mars 2019 10:56, Stefano Garzarella a
écrit :
> Using IEC binary prefixes in order to make the code more readable,
> with the exception of DEFAULT_LOG_SIZE because it's passed to
> stringify().
>
> Signed-off-by: Stefano Garzarella
> ---
> block/vhdx-log.c | 2 +-
> block/vhdx.c
From: Philippe Mathieu-Daudé
This fixes when configuring with --without-default-devices:
$ qemu-system-mips64 -bios /dev/null -M malta
qemu-system-mips64: Unsupported NIC model: pcnet
Fixes: 7c28b925b7e
Signed-off-by: Philippe Mathieu-Daudé
Message-Id: <20190316200818.8265-7-phi...@redhat.
When virtio-vga was added, the intention was to only support it for
those machines where the firmware does not know about virtio-gpu,
and supported VGA legacy hardware before virtio-{gpu,vga} were
introduced.
The Kconfig switch however enabled virtio-vga for all machines with
a PCI bus, and libvir
From: Philippe Mathieu-Daudé
This fixes when configuring with --without-default-devices:
$ qemu-system-ppc -M prep
qemu-system-ppc: Machine type 'prep' is deprecated: use 40p machine type
instead
qemu-system-ppc: Unknown device 'isa-pcspk' for bus 'ISA'
Fixes: dd0ff8191ab
Signed-off-by:
From: Philippe Mathieu-Daudé
This fixes when configuring with CONFIG_PCI_DEVICES=n:
$ qemu-system-ppc64 -bios /dev/null -M bamboo
qemu-system-ppc64: Unsupported NIC model: e1000
Fixes: 7c28b925b7e
Signed-off-by: Philippe Mathieu-Daudé
Acked-by: David Gibson
Message-Id: <20190316200818.826
bdrv_replace_child() calls bdrv_check_perm() with error_abort on
loosening permissions. However file-locking operations may fail even
in this case, for example on NFS. And this leads to Qemu crash.
Let's ignore such errors, as we do already on permission update commit
and abort.
Signed-off-by: Vl
From: Philippe Mathieu-Daudé
This fixes when configuring with --without-default-devices:
$ qemu-system-mips64el -bios /dev/null -M fulong2e
qemu-system-mips64el: Unknown device 'ati-vga' for bus 'PCI'
Aborted (core dumped)
(gdb) bt
#0 0x75a2753f in __GI_raise (sig=sig@entry=6
Le mer. 27 mars 2019 13:32, Ernest Esene a écrit :
> Set category and describe DIMM devices
>
> Signed-off-by: Ernest Esene
>
> ---
> v2:
> * split into separate patches
> ---
> hw/mem/nvdimm.c | 1 +
> hw/mem/pc-dimm.c | 1 +
> 2 files changed, 2 insertions(+)
>
> diff --git a/hw/mem/nvdimm
The result of this typo would be that "select_foo" would be treated as a
"select"
keyword followed by "_foo". Nothing too bad, but easy to fix so let's be clean.
Signed-off-by: Paolo Bonzini
---
scripts/minikconf.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/mi
From: Philippe Mathieu-Daudé
This fixes when configuring with CONFIG_PCI_DEVICES=n:
$ qemu-system-sh4 -M r2d
qemu-system-sh4: Unsupported NIC model: rtl8139
Fixes: 7ab58d4c84
Signed-off-by: Philippe Mathieu-Daudé
Message-Id: <20190316200818.8265-13-phi...@redhat.com>
Signed-off-by: Paolo B
On 13/03/2019 17.31, Jason J. Herne wrote:
> Create a new header for basic architecture specific definitions and add a
> mapping of low core memory. This mapping will be used by the real dasd boot
> process.
>
> Signed-off-by: Jason J. Herne
> Acked-by: Cornelia Huck
> ---
> pc-bios/s390-ccw/ma
From: Philippe Mathieu-Daudé
This fixes when configuring with CONFIG_PCI_DEVICES=n:
$ qemu-system-hppa
qemu-system-hppa: Unsupported NIC model: e1000
Fixes: 9483cf27dd
Signed-off-by: Philippe Mathieu-Daudé
Message-Id: <20190316200818.8265-14-phi...@redhat.com>
Signed-off-by: Paolo Bonzini
This ensures that softmmu directories are culled after a
"./configure --target-list=x86_64-linux-user".
Reviewed-by: Stefano Garzarella
Reviewed-by: Eric Blake
Signed-off-by: Paolo Bonzini
---
Makefile | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Makefile b/Makefile
Le mer. 27 mars 2019 10:56, Stefano Garzarella a
écrit :
> IEC binary prefixes are already defined in "qemu/units.h",
> so we can remove redundant definitions in "block/vhdx.h".
>
> Signed-off-by: Stefano Garzarella
> ---
> block/vhdx.c | 3 ++-
> block/vhdx.h | 6 +-
> 2 files changed, 3 i
Le mer. 27 mars 2019 13:23, Ernest Esene a écrit :
> Set category and describe IPMI devices
>
> Signed-off-by: Ernest Esene
>
> ---
> v2:
> * split into different patches
> * change category and description for management controllers
> ---
> hw/ipmi/ipmi_bmc_extern.c | 2 ++
> hw/ipmi/ipmi_
On Wed, Mar 27, 2019 at 01:22:18PM +0100, Ernest Esene wrote:
> Set category and describe IPMI devices
>
> Signed-off-by: Ernest Esene
Reviewed-by: Corey Minyard
Thanks!
-corey
>
> ---
> v2:
> * split into different patches
> * change category and description for management controllers
With aio=thread, adaptive polling makes latency worse rather than
better, because it delays the execution of the ThreadPool's
completion bottom half.
event_notifier_poll() does run while polling, detecting that
a bottom half was scheduled by a worker thread, but because
ctx->notifier is explicitly
On 13/03/2019 17.31, Jason J. Herne wrote:
> Now that we have a Channel I/O library let's modify virtio boot code to
> make use of it for running channel programs.
>
> Signed-off-by: Jason J. Herne
> Reviewed-by: Cornelia Huck
> ---
> pc-bios/s390-ccw/virtio.c | 57
> ++
Remove a space before bracket to fix checkpatch error
"ERROR: space prohibited between function name and open parenthesis".
Signed-off-by: Jules Irenge
---
This v2 version includes fix of all error of space on function and paranthesis
in this file
target/mips/cp0_timer.c | 12 ++--
1 fi
1 - 100 of 249 matches
Mail list logo
