Signed-off-by: Gerd Hoffmann
Reviewed-by: Daniel P. Berrangé
Message-id: 20190220100235.20914-1-kra...@redhat.com
---
ui/kbd-state.c | 16 ++--
1 file changed, 10 insertions(+), 6 deletions(-)
diff --git a/ui/kbd-state.c b/ui/kbd-state.c
index ac14add70eab..f3ab2d7a665d 100644
---
From: Marc-André Lureau
Inform the front-end of disconnected state (spice client
disconnected).
This will wakeup the source handler immediately, so it can detect the
disconnection asap.
Signed-off-by: Marc-André Lureau
Tested-by: Victor Toso
Message-id:
From: Lukáš Hrázký
Calls the new SPICE QXL interface function spice_qxl_set_device_info to
set the hardware address of the graphics device represented by the QXL
interface (e.g. a PCI path) and the device display IDs (the IDs of the
device's monitors that belong to this QXL interface).
Also
From: Marc-André Lureau
GIO is required for the "-display spice-app" backend.
Signed-off-by: Marc-André Lureau
Tested-by: Victor Toso
Message-id: 20190221110703.5775-9-marcandre.lur...@redhat.com
Signed-off-by: Gerd Hoffmann
---
configure | 13 +
1 file changed, 13 insertions(+)
From: Marc-André Lureau
The Spice server doesn't like to be started or stopped twice . It
aborts with:
(process:6191): Spice-ERROR **: 19:29:35.912:
red-worker.c:623:handle_dev_start: assertion `!worker->running' failed
It's easy to avoid that situation since qemu spice_display_is_running
From: Marc-André Lureau
spice_server_vm_start/stop() was added to help migration state (commit
f5bb039c6d97ef3e664094eab3c9a4dc1824ed73).
However, a paused VM could keep running the spice server. This will
allow a Spice client to keep sending commands to a spice chardev. This
allows to
The following changes since commit 2e68b8620637a4ee8c79b5724144b726af1e261b:
Merge remote-tracking branch 'remotes/dgibson/tags/ppc-for-4.0-20190219' into
staging (2019-02-18 16:20:13 +)
are available in the git repository at:
git://git.kraxel.org/qemu tags/ui-20190222-pull-request
From: Marc-André Lureau
Signed-off-by: Marc-André Lureau
Tested-by: Victor Toso
Message-id: 20190221110703.5775-10-marcandre.lur...@redhat.com
Signed-off-by: Gerd Hoffmann
---
qapi/ui.json | 25 +
1 file changed, 25 insertions(+)
diff --git a/qapi/ui.json
Stephen Checkoway writes:
>> On Feb 20, 2019, at 03:55, Laszlo Ersek wrote:
>>
>> I would strongly prefer if the guest-side view wouldn't change at all.
>
> It sounds like sector protection isn't something you want and it's not
László is content with the status quo, but I'm not.
> something
On 22/02/2019 04:31, Launchpad Bug Tracker wrote:
> I'd like to ask for the addition of option '--targets' to scripts/qemu-
> binfmt-conf.sh, in order to allow registering the interpreters for the
> given list of architectures only, instead of using all of the ones
> defined in qemu_target_list.
Hi Eric,
Can't we still use one single memory map and update the base of every entry
following VIRT_MEM? So that we don't need to split memory map or the
enumeration definition, neither do we need to copy a15memmap into the extended
memmap.
Thanks,
Heyi
On 2019/2/21 6:39, Eric Auger
David Gibson writes:
> On Thu, Feb 21, 2019 at 05:31:30PM +0100, Markus Armbruster wrote:
>> Alex Bennée writes:
>>
>> > Markus Armbruster writes:
>> >
>> >> Machine "ref405ep" maps its flash memory at address 2^32 - image size.
>> >> Image size is rounded up to the next multiple of 64KiB.
Philippe Mathieu-Daudé writes:
> On 2/21/19 10:38 AM, Peter Maydell wrote:
>> On Thu, 21 Feb 2019 at 09:22, Markus Armbruster wrote:
>>> Double-checking... you want me to keep goto reset_flash, like this:
>>>
>>> @@ -623,8 +617,8 @@ static void pflash_write(PFlashCFI01 *pfl, hwaddr
>>> offset,
On Fri, 22 Feb 2019 at 14:21, Michael S. Tsirkin wrote:
>
> On Fri, Feb 22, 2019 at 10:47:03AM +0800, Yongji Xie wrote:
> > > > +
> > > > +To track inflight I/O, the queue region should be processed as follows:
> > > > +
> > > > +When receiving available buffers from the driver:
> > > > +
> > > >
On Fri, Feb 22, 2019 at 07:37:02AM +0100, Marc-André Lureau wrote:
> Hi
>
> On Fri, Feb 22, 2019 at 4:14 AM Peter Xu wrote:
> >
> > We were pushing the context until right before running the gmainloop.
> > Now since we have everything unconditionally, we can move this
> > earlier.
> >
> > One
On Fri, Feb 22, 2019 at 07:29:09AM +0100, Marc-André Lureau wrote:
[...]
> > diff --git a/iothread.c b/iothread.c
> > index 6e297e9ef1..6fa87876e0 100644
> > --- a/iothread.c
> > +++ b/iothread.c
> > @@ -65,7 +65,7 @@ static void *iothread_run(void *opaque)
> > * We must check the
On Fri, Feb 22, 2019 at 07:25:16AM +0100, Marc-André Lureau wrote:
> Hi
>
> On Fri, Feb 22, 2019 at 4:14 AM Peter Xu wrote:
> >
> > Only sending an init-done message using lock+cond seems an overkill to
> > me. Replacing it with a simpler semaphore.
> >
> > Meanwhile, init the semaphore
Hi
On Fri, Feb 22, 2019 at 4:14 AM Peter Xu wrote:
>
> We were pushing the context until right before running the gmainloop.
> Now since we have everything unconditionally, we can move this
> earlier.
>
> One benefit is that now it's done even before init_done_sem, so as
> long as the iothread
On Fri, Feb 22, 2019 at 4:14 AM Peter Xu wrote:
>
> Since we've have the gcontext always there, create the main loop
> altogether. The iothread_run() is even cleaner.
>
> Signed-off-by: Peter Xu
Reviewed-by: Marc-André Lureau
> ---
> iothread.c | 12 +++-
> 1 file changed, 3
Hi
On Fri, Feb 22, 2019 at 4:14 AM Peter Xu wrote:
>
> In existing code we create the gcontext dynamically at the first
> access of the gcontext from caller. That can bring some complexity
> and potential races during using iothread. Since the context itself
> is not that big a resource, and
Hi
On Fri, Feb 22, 2019 at 4:14 AM Peter Xu wrote:
>
> Only sending an init-done message using lock+cond seems an overkill to
> me. Replacing it with a simpler semaphore.
>
> Meanwhile, init the semaphore unconditionally, then we can destroy it
> unconditionally too in finalize which seems
For priv levels 1 & 2, we were doing so from do_ibranch_priv.
Signed-off-by: Richard Henderson
---
target/hppa/translate.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/target/hppa/translate.c b/target/hppa/translate.c
index b4fd307b77..dad8ce563c 100644
---
On Fri, Feb 22, 2019 at 10:47:03AM +0800, Yongji Xie wrote:
> > > +
> > > +To track inflight I/O, the queue region should be processed as follows:
> > > +
> > > +When receiving available buffers from the driver:
> > > +
> > > +1. Get the next available head-descriptor index from available
On 21/02/2019 19.14, Philippe Mathieu-Daudé wrote:
> On 2/21/19 12:24 PM, Thomas Huth wrote:
>> Both functions, object_initialize() and object_property_add_child() increase
>> the reference counter of the new object, so one of the references has to be
>> dropped afterwards to get the reference
The first patch is via inspection. Linux only uses priv
levels 0 and 3, and I suspect that HP-UX is the same.
The second patch comes from examining traces.
r~
Richard Henderson (2):
target/hppa: Do not return freed temporary
target/hppa: Optimize blr r0,rn
target/hppa/translate.c | 21
---
ui/spice-app.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/ui/spice-app.c b/ui/spice-app.c
index 4f5229f3ee..925b27b708 100644
--- a/ui/spice-app.c
+++ b/ui/spice-app.c
@@ -181,6 +181,8 @@ static void spice_app_display_init(DisplayState *ds,
DisplayOptions *opts)
We can eliminate an extra TB in this case, which merely
loads a "return address" into rn.
Signed-off-by: Richard Henderson
---
target/hppa/translate.c | 16 ++--
1 file changed, 10 insertions(+), 6 deletions(-)
diff --git a/target/hppa/translate.c b/target/hppa/translate.c
index
This requires VSX, not just Altivec, so Power7 or later.
Signed-off-by: Richard Henderson
---
At present there are no tunables that can avoid the 64-bit element
load/store requirement. As with requiring AVX1 for x86 hosts, I'm
not sure it's worth inventing such a tunable for pre-power7 hosts.
Philippe Mathieu-Daudé writes:
> As Thomas Huth explained:
> "Both functions, object_initialize() and object_property_add_child()
> increase the reference counter of the new object, so one of the
> references has to be dropped afterwards to get the reference counting
> right. Otherwise the child
Hi,
> Would something like that be helpful?
>
> diff --git a/ui/spice-app.c b/ui/spice-app.c
> index 4f5229f3ee..69f92e440c 100644
> --- a/ui/spice-app.c
> +++ b/ui/spice-app.c
> @@ -181,6 +181,7 @@ static void spice_app_display_init(DisplayState
> *ds, DisplayOptions *opts)
>
This allows configure the display resolution which the vgpu should use.
The information will be passed to the guest using EDID, so the mdev
driver must support the vfio edid region for this to work.
Signed-off-by: Gerd Hoffmann
---
hw/vfio/pci.h | 2 ++
hw/vfio/display.c | 12 ++--
This patch adds EDID support to the vfio display (aka vgpu) code.
When supported by the mdev driver qemu will generate a EDID blob
and pass it on using the new vfio edid region. The EDID blob will
be updated on UI changes (i.e. window resize), so the guest can
adapt.
Signed-off-by: Gerd Hoffmann
Kick the display link up event with a 0.1 sec delay,
so the guest has a chance to notice the link down first.
Signed-off-by: Gerd Hoffmann
---
include/hw/vfio/vfio-common.h | 1 +
hw/vfio/display.c | 26 +++---
2 files changed, 24 insertions(+), 3 deletions(-)
The 5.0 linux kernel header update finally landed in master. So this
series has no unmerged dependencies any more. Rebasing and re-sending
for merge.
This series adds EDID support to the qemu vfio display code. Various
display-reladed information -- most importantly the display resolution
Hi,
> This is the vdagent using installation like this:
>
> https://www.ovirt.org/develop/infra/testing/spice.html
>
> ie. vdservice install, net start vdservice?
If the page says so, probably.
I've tested the agent setup with linux only, where everything happens
automatically, you only
From: Eric Auger
We introduce the vfio_init_container_type() helper.
It computes the highest usable iommu type and then
set the container and the iommu type.
Its usage in vfio_connect_container() makes the code
ready for addition of new iommu types.
Signed-off-by: Eric Auger
Reviewed-by: Greg
A kernel bug was introduced in v4.15 via commit 71a7d3d78e3c which
adds a test for address space wrap-around in the vfio DMA unmap path.
Unfortunately due to overflow, the kernel detects an unmap of the last
page in the 64-bit address space as a wrap-around. In QEMU, a Q35
guest with VT-d
The following changes since commit fc3dbb90f2eb069801bfb4cfe9cbc83cf9c5f4a9:
Merge remote-tracking branch 'remotes/jnsnow/tags/bitmaps-pull-request' into
staging (2019-02-21 13:09:33 +)
are available in the Git repository at:
git://github.com/awilliam/qemu-vfio.git
On 21/02/2019 19.38, Philippe Mathieu-Daudé wrote:
> As Thomas Huth explained:
> "Both functions, object_initialize() and object_property_add_child()
> increase the reference counter of the new object, so one of the
> references has to be dropped afterwards to get the reference counting
> right.
On Thu, Feb 21, 2019 at 10:10:08PM -0500, Michael S. Tsirkin wrote:
> On Fri, Feb 22, 2019 at 11:04:05AM +0800, Jason Wang wrote:
> >
> > On 2019/2/22 上午9:35, Michael S. Tsirkin wrote:
> > > On Thu, Feb 21, 2019 at 05:40:22PM +0800, Jason Wang wrote:
> > > > On 2019/2/21 下午4:18, Yuri Benditovich
Public bug reported:
I'd like to ask for the addition of option '--targets' to scripts/qemu-
binfmt-conf.sh, in order to allow registering the interpreters for the
given list of architectures only, instead of using all of the ones
defined in qemu_target_list. The following is a possible patch
On Thu, Feb 21, 2019 at 11:39:32AM +0100, Marc-André Lureau wrote:
> Hi
>
> On Thu, Feb 21, 2019 at 9:00 AM Peter Xu wrote:
> >
> > On Wed, Feb 20, 2019 at 05:06:25PM +0100, Marc-André Lureau wrote:
> > > Another thread may acquire the glib context (temporarily) before
> > >
We were pushing the context until right before running the gmainloop.
Now since we have everything unconditionally, we can move this
earlier.
One benefit is that now it's done even before init_done_sem, so as
long as the iothread user calls iothread_create() and completes, we
know that the thread
When I first read the iothread code, the gcontext confused me for
quite a while. Meanwhile, I've been tackling with some races due to
this complexity as well. How much we'll pay for creating the gcontext
unconditionally? Do we really need this flexibitily (or is it really
a flexibility after
In existing code we create the gcontext dynamically at the first
access of the gcontext from caller. That can bring some complexity
and potential races during using iothread. Since the context itself
is not that big a resource, and we won't have millions of iothread,
let's simply create the
Only sending an init-done message using lock+cond seems an overkill to
me. Replacing it with a simpler semaphore.
Meanwhile, init the semaphore unconditionally, then we can destroy it
unconditionally too in finalize which seems cleaner.
Signed-off-by: Peter Xu
---
include/sysemu/iothread.h |
Since we've have the gcontext always there, create the main loop
altogether. The iothread_run() is even cleaner.
Signed-off-by: Peter Xu
---
iothread.c | 12 +++-
1 file changed, 3 insertions(+), 9 deletions(-)
diff --git a/iothread.c b/iothread.c
index 6fa87876e0..9abdbace66 100644
On Fri, Feb 22, 2019 at 11:04:05AM +0800, Jason Wang wrote:
>
> On 2019/2/22 上午9:35, Michael S. Tsirkin wrote:
> > On Thu, Feb 21, 2019 at 05:40:22PM +0800, Jason Wang wrote:
> > > On 2019/2/21 下午4:18, Yuri Benditovich wrote:
> > >
> > > For 1.0 device, we can fix the queue_enable, but
From: Changpeng Liu
Signed-off-by: Changpeng Liu
Reviewed-by: Stefan Hajnoczi
Reviewed-by: Stefano Garzarella
Reviewed-by: Michael S. Tsirkin
Message-Id: <1547615970-23545-2-git-send-email-changpeng@intel.com>
[PMD: this patch was first (incorrectly) introduced as a56de056c91f8]
From: Laszlo Ersek
The roms/edk2 submodule can help with three goals:
- build the OVMF and ArmVirtQemu virtual UEFI firmware platforms (to be
implemented later),
- build the EfiRom tool on the fly, which is used in roms/Makefile, for
building the "efirom" target,
- build UEFI test
On 2019/2/22 上午9:35, Michael S. Tsirkin wrote:
On Thu, Feb 21, 2019 at 05:40:22PM +0800, Jason Wang wrote:
On 2019/2/21 下午4:18, Yuri Benditovich wrote:
For 1.0 device, we can fix the queue_enable, but for 0.9x device how do
you enable one specific queue in this case?
From: Laszlo Ersek
Introduce the following build scripts under "tests/uefi-test-tools":
* "build.sh" builds a single module (a UEFI application) from
UefiTestToolsPkg, for a single QEMU emulation target.
"build.sh" relies on cross-compilers when the emulation target and the
build host
From: Laszlo Ersek
The "bios-tables-test" program in QEMU's test suite locates the RSD PTR
ACPI table in guest RAM, and (chasing pointers to other ACPI tables)
performs various sanity checks on the QEMU-generated and
firmware-installed tables.
Currently this set of test cases doesn't work with
Now setting, but not relying upon, env->hflags.
Reviewed-by: Alex Bennée
Signed-off-by: Richard Henderson
---
v2: Fixed partial conversion to assignment to env->hflags.
---
target/arm/internals.h | 1 +
linux-user/syscall.c | 1 +
target/arm/cpu.c | 1 +
This is the payoff.
>From perf record -g data of ubuntu 18 boot and shutdown:
BEFORE:
- 23.02% 2.82% qemu-system-aar [.] helper_lookup_tb_ptr
- 20.22% helper_lookup_tb_ptr
+ 10.05% tb_htable_lookup
- 9.13% cpu_get_tb_cpu_state
3.20% aa64_va_parameters_both
On Fri, 22 Feb 2019 at 01:27, Michael S. Tsirkin wrote:
>
> On Mon, Feb 18, 2019 at 06:27:42PM +0800, elohi...@gmail.com wrote:
> > From: Xie Yongji
> >
> > This patch introduces two new messages VHOST_USER_GET_INFLIGHT_FD
> > and VHOST_USER_SET_INFLIGHT_FD to support transferring a shared
> >
From: Laszlo Ersek
Add UEFI-bootable qcow2-compressed ISO images built from:
tests/uefi-test-tools/UefiTestToolsPkg/BiosTablesTest
Cc: "Michael S. Tsirkin"
Cc: Ard Biesheuvel
Cc: Gerd Hoffmann
Cc: Igor Mammedov
Cc: Philippe Mathieu-Daudé
Cc: Shannon Zhao
Signed-off-by: Laszlo Ersek
The following changes since commit fc3dbb90f2eb069801bfb4cfe9cbc83cf9c5f4a9:
Merge remote-tracking branch 'remotes/jnsnow/tags/bitmaps-pull-request' into
staging (2019-02-21 13:09:33 +)
are available in the Git repository at:
git://git.kernel.org/pub/scm/virt/kvm/mst/qemu.git
We will use these to minimize the computation for every call to
cpu_get_tb_cpu_state. For now, the env->hflags variable is not used.
Reviewed-by: Alex Bennée
Signed-off-by: Richard Henderson
---
v3: Do not cache VECLEN, VECSTRIDE, VFPEN.
Move HANDLER and STACKCHECK to rebuild_hflags_a32.
Changes since v2:
* Do not cache VECLEN, VECSTRIDE, VFPEN.
These variables come from VFP_FPSCR and VFP_FPEXC, not from
system control registers.
* Move HANDLER and STACKCHECK to rebuild_hflags_a32,
instead of building them in rebuild_hflags_common.
Changes since v1:
* Apparently
From: Philippe Mathieu-Daudé
Commit a56de056c91f8 squashed the following two unrelated commits
at once:
- "contrib/vhost-user-blk: fix the compilation issue"
(Message-Id: 1547615970-23545-2-git-send-email-changpeng@intel.com)
- "i386/kvm: ignore masked irqs when update msi routes"
From: Wei Yang
[get|set]_addr are two counterpart to access PCDIMMDevice.addr.
Since we have already set up a property PC_DIMM_ADDR_PROP for this
field and use this mechanism in set_addr, it would be more proper to use
the same mechanism in get_addr.
This patch uses object_property_get_uint()
From: Laszlo Ersek
Building the EfiRom utility from "roms/edk2/BaseTools" should make
"roms/Makefile" more self-contained. Otherwise, we'd call the system-wide
EfiRom for building the combined iPXE option ROMs, but call the sibling
utilities from "roms/edk2/BaseTools" for building "roms/edk2"
From: Peter Xu
When we are with intel-iommu device and with IR on, KVM will register
an IEC notifier to detect interrupt updates from the guest and we'll
kick off kvm_update_msi_routes_all() when it happens to make sure
kernel IRQ cache is matching the latest.
Though,
On Thu, Feb 21, 2019 at 05:40:22PM +0800, Jason Wang wrote:
>
> On 2019/2/21 下午4:18, Yuri Benditovich wrote:
>
> For 1.0 device, we can fix the queue_enable, but for 0.9x device how
> do
> you enable one specific queue in this case? (setting status?)
>
>
> Do I understand
On 02/21/2019 06:18 PM, Dr. David Alan Gilbert wrote:
* Wei Wang (wei.w.w...@intel.com) wrote:
On 02/20/2019 09:12 PM, Dr. David Alan Gilbert wrote:
* Wang, Wei W (wei.w.w...@intel.com) wrote:
On Friday, December 14, 2018 7:17 PM, Dr. David Alan Gilbert wrote:
On 12/14/2018 05:56 PM, Dr.
On 2/20/19 12:13 PM, Philippe Mathieu-Daudé wrote:
> On 2/20/19 11:03 AM, Marc-André Lureau wrote:
>> Hi
>>
>> On Wed, Feb 20, 2019 at 2:03 AM Philippe Mathieu-Daudé
>> wrote:
>>>
>>> The backend should not return a negative length to read.
>>> We will later change the prototype of
Hi Daniel,
On 2/15/19 4:57 PM, Daniel P. Berrangé wrote:
> From: "Daniel P. Berrange"
>
> Add an authorization backend that talks to PAM to check whether the user
> identity is allowed. This only uses the PAM account validation facility,
> which is essentially just a check to see if the
On 20/02/2019 11:24, Yuval Shaia wrote:
On Wed, Feb 20, 2019 at 12:13:45PM +0100, Gerd Hoffmann wrote:
From: Liam Merwick
Add an assert and an explicit check before the two callers to
usb_ep_get() in the USB redirector code to ensure the device
passed in is not NULL.
Signed-off-by: Liam
On 2/18/19 4:25 PM, Philippe Mathieu-Daudé wrote:
> On 2/18/19 9:05 PM, Eric Blake wrote:
>> [adding Eduardo for some python 2-vs-3 advice]
>
> And Cleber.
>
>>
>> On 2/18/19 1:59 PM, Andrey Shinkevich wrote:
>>> To write one byte to disk, Python2 may use 'chr' type.
>>> In Python3,
On 2/21/19 2:59 PM, Emilio G. Cota wrote:
> Should have done so the first time. Here it is:
>
> (gdb) r
> Starting program: /data/src/qemu/build/arm-softmmu/qemu-system-arm -machine
> type=virt -nographic -m 4096 -netdev
On Thu, Feb 21, 2019 at 22:36:25 +, Alex Bennée wrote:
> Emilio G. Cota writes:
> > This brings my arm-softmmu bootup+shutdown test to an early death:
>
> Can you retry with --enable-tcg-debug?
Should have done so the first time. Here it is:
(gdb) r
On Thu, Feb 21, 2019 at 12:24:48PM +0100, Thomas Huth wrote:
> Both functions, object_initialize() and object_property_add_child() increase
> the reference counter of the new object, so one of the references has to be
> dropped afterwards to get the reference counting right. Otherwise the child
>
On Thu, Feb 21, 2019 at 09:25:46AM +, Daniel P. Berrangé wrote:
> On Tue, Feb 19, 2019 at 01:55:01PM +1100, David Gibson wrote:
> > On Mon, Feb 18, 2019 at 11:43:49PM +0530, P J P wrote:
> > > From: Prasad J Pandit
> > >
> > > On ppc hosts, hypervisor shares following system attributes
> > >
On Wed, 20 Feb 2019 02:53:18 +0530
Kirti Wankhede wrote:
> - Migration function are implemented for VFIO_DEVICE_TYPE_PCI device.
> - Added SaveVMHandlers and implemented all basic functions required for live
> migration.
> - Added VM state change handler to know running or stopped state of VM.
Emilio G. Cota writes:
> On Tue, Feb 19, 2019 at 15:34:18 -0800, Richard Henderson wrote:
>> Changes since v1:
>> * Apparently I had started a last-minute API change, and failed to
>> covert all of the users, and also failed to re-test afterward.
>> * Retain assertions for
On Thu, Feb 21, 2019 at 05:31:30PM +0100, Markus Armbruster wrote:
> Alex Bennée writes:
>
> > Markus Armbruster writes:
> >
> >> Machine "ref405ep" maps its flash memory at address 2^32 - image size.
> >> Image size is rounded up to the next multiple of 64KiB. Useless,
> >> because
On Wed, 20 Feb 2019 02:53:16 +0530
Kirti Wankhede wrote:
> - Defined MIGRATION region type and sub-type.
> - Used 2 bits to define VFIO device states.
> Bit 0 => 0/1 => _STOPPED/_RUNNING
> Bit 1 => 0/1 => _RESUMING/_SAVING
> Combination of these bits defines VFIO device's state
On Thu, 21 Feb 2019 19:13:23 +0100
Knut Omang wrote:
> Claim ACS support in the generic PCIe root port to allow
> passthrough of individual functions of a device to different
> guests (in a nested virt.setting) with VFIO.
> Without this patch, all functions of a device, such as all VFs of
> an
On Thu, 21 Feb 2019 19:13:22 +0100
Knut Omang wrote:
> Implementing an ACS capability on downstream ports and multifunction
> endpoints indicates isolation and IOMMU visibility to a finer
> granularity. This creates smaller IOMMU groups in the guest and thus
> more flexibility in assigning
On Tue, Feb 19, 2019 at 15:34:18 -0800, Richard Henderson wrote:
> Changes since v1:
> * Apparently I had started a last-minute API change, and failed to
> covert all of the users, and also failed to re-test afterward.
> * Retain assertions for --enable-debug-tcg.
This brings my
On Thu, Feb 21, 2019 at 7:09 PM Jan Kiszka wrote:
> On 21.02.19 17:05, Eric Blake wrote:
> > On 2/21/19 9:53 AM, David Kiarie wrote:
> >> the occurrence of my name and email on the files below may have led to
> >> some confusion in the reporting of a few recent bugs.
> >>
> >> i have therefore
Hi Alex,
On 2/21/19 7:48 PM, Alex Bennée wrote:
> It looks like there was going to be code to check we had some sort of
> alignment so lets replace it with an actual check. This is a bit more
> useful than the enigmatic "failed to read the initial flash content"
> when we attempt to read the
Hi Yan,
Thanks for working on this!
On Tue, 19 Feb 2019 16:50:54 +0800
Yan Zhao wrote:
> This patchset enables VFIO devices to have live migration capability.
> Currently it does not support post-copy phase.
>
> It follows Alex's comments on last version of VFIO live migration patches,
>
Il giorno gio 21 feb 2019 alle 19:00 Paolo Bonzini ha
scritto:
> On 21/02/19 16:44, Stefano Garzarella wrote:
> >> +
> > Hi Paolo,
> > I'm playing with Kconfig but with a simple configuration
> > (./configure --target-list=x86_64-softmmu --disable-docs) the build
> fails:
> > /usr/bin/ld:
Patchew URL: https://patchew.org/QEMU/20190213234907.24173-1-js...@redhat.com/
Hi,
This series failed the docker-mingw@fedora build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
=== TEST SCRIPT BEGIN ===
Laszlo Ersek writes:
> On 02/21/19 19:48, Alex Bennée wrote:
>> It looks like there was going to be code to check we had some sort of
>> alignment so lets replace it with an actual check. This is a bit more
>> useful than the enigmatic "failed to read the initial flash content"
>> when we
> On Feb 20, 2019, at 03:55, Laszlo Ersek wrote:
>
> I would strongly prefer if the guest-side view wouldn't change at all.
It sounds like sector protection isn't something you want and it's not
something I currently need so unless that changes, I probably won't do anything
with it.
My
On Thu, Feb 21, 2019 at 12:08:12PM -0600, Eric Blake wrote:
> On 2/21/19 11:37 AM, Sergio Lopez wrote:
> > This parameter is analogous to convert's "-C", making use of
> > bdrv_co_copy_range().
>
> The last time I tried to patch 'qemu-img dd', it was pointed out that it
> already has several bugs
The following changes since commit fc3dbb90f2eb069801bfb4cfe9cbc83cf9c5f4a9:
Merge remote-tracking branch 'remotes/jnsnow/tags/bitmaps-pull-request' into
staging (2019-02-21 13:09:33 +)
are available in the Git repository at:
https://github.com/rth7680/qemu.git tags/pull-hppa-20190221
The last update to this file was 9 years ago. In the meantime,
4 of the 6 ideas have actually been completed. The lat two do
not actually make sense anymore.
Suggested-by: Thomas Huth
Signed-off-by: Richard Henderson
---
tcg/TODO | 14 --
1 file changed, 14 deletions(-)
delete
Many of the devices on the Musca board live behind TrustZone
Peripheral Protection Controllers (PPCs); add models of the
PPCs, using a similar scheme to the MPS2 board models.
This commit wires up the PPCs with "unimplemented device"
stubs behind them in the correct places in the address map.
On 02/21/19 19:48, Alex Bennée wrote:
> It looks like there was going to be code to check we had some sort of
> alignment so lets replace it with an actual check. This is a bit more
> useful than the enigmatic "failed to read the initial flash content"
> when we attempt to read the number of bytes
The Musca-A and Musca-B1 development boards are based on the
SSE-200 subsystem for embedded. Implement an initial skeleton
model of these boards, which are similar but not identical.
This commit creates the board model with the SSE and the IRQ
splitters to wire IRQs up to its two CPUs. As yet
From: David Hildenbrand
Especially when dealing with out-of-line gvec helpers, it is often
helpful to specify some vector pointers as constant. E.g. when
we have two inputs and one output, marking the two inputs as consts
pointers helps to avoid bugs.
Const pointers can be specified via "cptr",
Wire up the two PL011 UARTs in the Musca board.
Signed-off-by: Peter Maydell
Reviewed-by: Richard Henderson
---
hw/arm/musca.c | 34 +-
1 file changed, 29 insertions(+), 5 deletions(-)
diff --git a/hw/arm/musca.c b/hw/arm/musca.c
index 378912b7385..23aff43f4bc
From: Richard Henderson
Signed-off-by: Richard Henderson
Message-id: 20190215192302.27855-5-richard.hender...@linaro.org
Reviewed-by: Peter Maydell
[PMM: fixed a couple of comment typos]
Signed-off-by: Peter Maydell
---
target/arm/cpu.h | 10 +
target/arm/helper.h| 3
The following changes since commit fc3dbb90f2eb069801bfb4cfe9cbc83cf9c5f4a9:
Merge remote-tracking branch 'remotes/jnsnow/tags/bitmaps-pull-request' into
staging (2019-02-21 13:09:33 +)
are available in the Git repository at:
https://github.com/rth7680/qemu.git tags/pull-tcg-20190221
On 2/21/19 12:56 PM, Daniel P. Berrangé wrote:
> On Thu, Feb 21, 2019 at 03:39:15PM +0100, Erik Skultety wrote:
>> Hi,
>> I'm starting this thread in order to continue with the ongoing efforts to
>> bring actual integration testing to libvirt. Currently, the status quo is
>> that
>> we build
The region 0x4001 .. 0x4001 and its secure-only alias
at 0x5001... are for per-CPU devices. We implement this by
giving each CPU its own container memory region, where the
per-CPU devices live. Unfortunately, the alias region which
makes devices mapped at 0x4... addresses also appear
1 - 100 of 378 matches
Mail list logo
