Thanks for checking! ... so I'm closing this ticket now.
** Changed in: qemu
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1135567
Title:
QXL crashes a Wi
** Changed in: qemu
Assignee: Pradeep K Surisetty (pradeepkumars) => (unassigned)
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/888016
Title:
RHEL 6.1 guest fails to boot with vhost
Status in
On 12.09.2017 15:28, Eric Blake wrote:
> On 09/12/2017 02:21 AM, Thomas Huth wrote:
[...]
>> I fail to see why we need a separate bus object here for each device.
>> The bus is only available one time, not multiple times, isn't it? So
>> there should also only be one bus object floating around, not
On Tue, 12 Sep 2017 15:05:56 -0300
Eduardo Habkost wrote:
> On Mon, Sep 11, 2017 at 05:06:00PM +0200, Igor Mammedov wrote:
> > On Mon, 11 Sep 2017 16:31:39 +0200
> > Thomas Huth wrote:
> >
> > > On 11.09.2017 14:53, Igor Mammedov wrote:
> > > > On Thu, 7 Sep 2017 11:22:42 +0200
> > > > Tho
On 12.09.2017 15:28, Eric Blake wrote:
> On 09/12/2017 02:29 AM, Thomas Huth wrote:
>> On 11.09.2017 19:19, Eric Blake wrote:
>>> Commit 2f8b2767 originally added qpci_plug_device_test() and
>>> qpci_unplug_acpi_device_test() as a pair, both in pci-pc.c.
>>> Later, commit cf716b31 moved one half of
There hasn't been a reply to my question in the last comment within
months, so I assume nobody cares about this anymore. So I'm closing this
ticket now...
** Changed in: qemu
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of qemu-
devel-ml,
There hasn't been a reply to my question in the last comment within
months, so I assume nobody cares about this anymore. So I'm closing this
ticket now...
** Changed in: qemu
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of qemu-
devel-ml,
** Changed in: qemu
Importance: Wishlist => Undecided
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/584146
Title:
Virtual fat breaks with -snapshot
Status in QEMU:
Incomplete
Status in qemu-k
There hasn't been a reply to my question in the last comment within
months, so I assume this has been fixed in upstream, too. Closing this
ticket now...
** Changed in: qemu
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml,
On 12.09.2017 15:32, Eric Blake wrote:
> On 09/12/2017 05:14 AM, Thomas Huth wrote:
>> On 11.09.2017 19:20, Eric Blake wrote:
>>> We have several callers that were formatting the argument strings
>>> themselves; consolidate this effort by adding new convenience
>>> functions directly in libqtest, a
On Tue, 12 Sep 2017 17:42:35 +0200
David Hildenbrand wrote:
> On 12.09.2017 14:43, Igor Mammedov wrote:
> > On Mon, 11 Sep 2017 17:21:40 +0200
> > David Hildenbrand wrote:
> >
> >> Specifying more than 1 CPU (e.g. -smp 5) leads to SIGP errors (the
> >> guest tries to bring these CPUs up but f
There hasn't been any comment about upstream QEMU within the last
months, so I assume this has been fixed there, too. Closing...
** Changed in: qemu
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to
On Mon, Sep 11, 2017 at 06:19:54PM +0100, Dr. David Alan Gilbert wrote:
> * Mark Cave-Ayland (mark.cave-ayl...@ilande.co.uk) wrote:
> > On 11/09/17 11:48, David Gibson wrote:
> >
> > > On Mon, Sep 11, 2017 at 10:30:33AM +0100, Dr. David Alan Gilbert wrote:
> > >> * Greg Kurz (gr...@kaod.org) wrote
On Sun, Sep 10, 2017 at 03:37:35PM +0100, Mark Cave-Ayland wrote:
> During local testing with TCG, intermittent errors were found when trying to
> migrate Darwin OS images.
>
> The underlying cause was that Darwin resets the decrementer value to fairly
> small values on each interrupt. cpu_ppc_set
On Mon, Sep 11, 2017 at 05:52:10PM +0100, Mark Cave-Ayland wrote:
> On 11/09/17 11:57, David Gibson wrote:
>
> > On Sun, Sep 10, 2017 at 03:37:34PM +0100, Mark Cave-Ayland wrote:
> >> This is referenced in cpu_ppc_handle_mmu_fault() and so should be included
> >> in the migration stream.
> >
> >
On 12.09.2017 18:06, Peter Maydell wrote:
On 12 September 2017 at 15:53, Sergey Smolov wrote:
Generally speaking, is it possible at "run time" to detect write accesses to
MIPS GPR registers?
If true, which parts of code should I look in?
We don't currently support tracing at that level, I'm a
On Mon, Sep 11, 2017 at 10:40:10AM +0530, Nikunj A Dadhania wrote:
> David Gibson writes:
>
> > On Wed, Sep 06, 2017 at 01:57:48PM +0530, Nikunj A Dadhania wrote:
> >> When the user does not provide the cpu topology, e.g. "-smp 4", machine
> >> fails to
> >> initialize 4 cpus. Compute the chip p
There hasn't been a reply to my question in comment #32 within
months, so I assume nobody cares about this anymore. So I'm closing this
ticket now...
** Changed in: qemu
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of qemu-
devel-ml, which
Signed-off-by: Gerd Hoffmann
Message-id: 20170828123933.30323-3-kra...@redhat.com
---
hw/display/qxl-render.c | 36 +---
1 file changed, 29 insertions(+), 7 deletions(-)
diff --git a/hw/display/qxl-render.c b/hw/display/qxl-render.c
index e1b3f05ecb..90e0865618 10
Instead pass around the address (aka offset into vga memory).
Add vga_read_* helper functions which apply vbe_size_mask to
the address, to make sure the address stays within the valid
range, similar to the cirrus blitter fixes (commits ffaf857778
and 026aeffcb4).
Impact: DoS for privileged guest
Don't reset window layout information (passed via virtio_gpu_ui_info) on
device reset, so the user interface window layout will be kept intact
over reboots. The head size and position was commented out already, so
this patch just drops the dead code. Additionally the enabled head mask
must be kep
vga display update mis-calculated the region for the dirty bitmap
snapshot in case split screen mode is used. This can trigger an
assert in cpu_physical_memory_snapshot_get_dirty().
Impact: DoS for privileged guest users.
Fixes: CVE-2017-13673
Fixes: fec5e8c92becad223df9d972770522f64aafdb72
Cc:
The chunk size sanity check in qxl_render_cursor works for
SPICE_CURSOR_TYPE_ALPHA cursors only. So support for
SPICE_CURSOR_TYPE_MONO cursors must be broken for ages without anyone
noticing. Most likely it simply isn't used any more by guest drivers.
Drop the dead code.
Signed-off-by: Gerd Hoff
The following changes since commit 223cd0e13f2e46078d7b573f0b8402bfbee339be:
Merge remote-tracking branch 'remotes/elmarco/tags/tidy-pull-request' into
staging (2017-08-31 15:52:43 +0100)
are available in the git repository at:
git://git.kraxel.org/qemu tags/vga-20170913-pull-re
On Mon, 11 Sep 2017 13:06:19 +0200
Marc-André Lureau wrote:
> Signed-off-by: Marc-André Lureau
> ---
> qapi-schema.json| 101 ---
> qapi/target.json| 104
>
> include/sysemu/arch_init.h
** No longer affects: qemu
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1300863
Title:
Qemu does not show all files on floppy or hard drive (MS DOS 6.22
guest)
Status in qemu package in Debian:
From: "Dr. David Alan Gilbert"
After migration the chain4 alias mapping added by 80763888 (in 2011)
might be missing, since there's no call to vga_update_memory_access
in the post_load after the registers are updated. Add it back.
Signed-off-by: Dr. David Alan Gilbert
Reviewed-by: Juan Quintel
On Mon, 11 Sep 2017 13:06:20 +0200
Marc-André Lureau wrote:
> Signed-off-by: Marc-André Lureau
> ---
> qapi/target.json | 6 ++
> 1 file changed, 6 insertions(+)
>
> diff --git a/qapi/target.json b/qapi/target.json
> index 3b73a9202f..12002b54d5 100644
> --- a/qapi/target.json
> +++ b/qapi
There hasn't been a reply to my question in the last comment within
months, so I assume nobody cares about this anymore. So I'm closing this
ticket now...
** Changed in: qemu
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of qemu-
devel-ml,
** Changed in: qemu
Assignee: benjamin_zb (zhuben1989) => (unassigned)
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1254940
Title:
qemu-KVM guest OS occurs many ext3-fs errors after multiple
On Mon, 11 Sep 2017 13:06:23 +0200
Marc-André Lureau wrote:
> It depends on TARGET_PPC || TARGET_ARM || TARGET_I386 || TARGET_S390X.
>
> Signed-off-by: Marc-André Lureau
> ---
> qapi-schema.json| 11 ---
> qapi/target.json| 12
> include/sysemu/arch
On Mon, 11 Sep 2017 13:06:22 +0200
Marc-André Lureau wrote:
> Signed-off-by: Marc-André Lureau
> ---
> qapi-schema.json | 38 -
> qapi/target.json | 39
> ++
> include/sysemu/arch_init.h
On 2017/9/12 0:39, Peter Maydell wrote:
+return kvm_vcpu_ioctl(CPU(cpu), KVM_ARM_SEI, &syndrome);
>>> This looks odd. If we don't have the RAS extension why do we need to do
>>> anything at all here ?
>> This is because Qemu may need to support non-RAS extension as discussed with
>> A
On Tue, 12 Sep 2017 16:01:49 +0200
Laurent Vivier wrote:
> and add a test case of dump-guest-memory without
> "[begin length]" parameters.
>
> Signed-off-by: Laurent Vivier
> Reviewed-by: Thomas Huth
> ---
> tests/test-hmp.c | 4
> 1 file changed, 4 insertions(+)
>
> diff --git a/tests/
There hasn't been a reply to my question in the last comment within
months, so I assume nobody cares about this anymore. So I'm closing this
ticket now...
** Changed in: qemu
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-m
Since the debian bug has been marked as fixed and there wasn't any
response to the question in my last comment, I assume this has been
fixed in upstream QEMU, too. So closing this ticket accordingly...
** Changed in: qemu
Status: Incomplete => Fix Released
--
You received this bug notific
There hasn't been a reply to my question in the last comment within
months, so I assume nobody cares about this anymore. So I'm closing this
ticket now...
** Changed in: qemu
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-m
According to the Fedora bug, this has been fixed. And since there wasn't
any reply to the question in my last comment, I assume nobody
experiences this issue anymore. So closing this ticket now...
** Changed in: qemu
Status: Incomplete => Fix Released
--
You received this bug notification
On Wed, 09/13 08:47, Thomas Huth wrote:
> Meta comment: Could we maybe also rename "tests/qemu-iotests" to
> "tests/iotests" ? The "qemu" prefix sounds always very superfluous to me
> here...
Sounds good, and saves typing for when this path is manually entered. But maybe
keep tests/qemu-iotests as
On Tue, 12 Sep 2017 12:17:51 +0200
Marc-André Lureau wrote:
> Hi Peter
>
> On Tue, Sep 12, 2017 at 5:33 AM, Peter Xu wrote:
> > On Mon, Sep 11, 2017 at 03:26:27PM +0200, Cornelia Huck wrote:
> >> It does not really make sense to dump memory that is not there.
> >>
> >> Moreover, that fixes a
This is maybe a duplicate of
https://bugs.launchpad.net/qemu/+bug/1714331 ... could you please try a
newer version of the OVMF firmware (if you're using it)?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/b
On Tue, Sep 12, 2017 at 07:11:34PM +0200, Paolo Bonzini wrote:
> On 12/09/2017 18:51, Daniel P. Berrange wrote:
> > Currently before submitting a series, devs should run checkpatch.pl
> > across each patch to be submitted. This can be automated using a
> > command such as:
> >
> > git rebase -i
Hi,
> @@ -287,6 +287,12 @@ static void
> virtio_gpu_resource_create_2d(VirtIOGPU *g,
> struct virtio_gpu_resource_create_2d c2d;
>
> VIRTIO_GPU_FILL_CMD(c2d);
> +
> +c2d.resource_id = le32_to_cpu(c2d.resource_id);
> +c2d.format = le32_to_cpu(c2d.format);
> +c2d.width = le
Is this still an issue with the latest version of QEMU (currently
v2.10), or could we close this ticket nowadays?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launc
If bkt->max == 0 and bkt->burst_length > 1 then we could have a
division by 0 in throttle_do_compute_wait(). That configuration is
however not permitted and is already detected by throttle_is_valid(),
but let's assert it in throttle_compute_wait() to make it explicit.
Found by Coverity (CID: 13810
The following changes since commit 619c200f6ce2f44fbc8a5732174530c3b4782aab:
Merge remote-tracking branch 'remotes/mcayland/tags/qemu-openbios-signed'
into staging (2017-09-11 11:44:30 +0100)
are available in the git repository at:
git://git.kraxel.org/qemu tags/ui-20170913-pu
Drop pixman submodule and support for the "internal" pixman build.
pixman should be reasonably well established meanwhile so we don't
need the fallback submodule any more. While being at it also drop
some #ifdefs for pixman versions older than what we require in
configure anyway.
Signed-off-by: G
Remove pixman switches from configure, should not be needed any more,
configure can figure by itself whenever pixman is needed or not.
Signed-off-by: Gerd Hoffmann
Message-id: 20170905140116.28181-3-kra...@redhat.com
---
configure | 24 ++--
1 file changed, 2 insertions(+), 2
virtio-gpu can trigger the assert added by commit "6905b93447 console:
add same surface replace pre-condition" in multihead setups (where
surface can be NULL for secondary displays). Allow surface being NULL.
Fixes: 6905b93447a42e606dfd126b90f75f4cd3c6fe94
Signed-off-by: Gerd Hoffmann
Reviewed-b
From: Alexander Graf
Some termcaps (found using SLES11SP1) use [? sequences. According to man
console_codes (http://linux.die.net/man/4/console_codes) the question mark
is a nop and should simply be ignored.
This patch does exactly that, rendering screen output readable when
outputting guest ser
Changes in v4:
(1) Use g_new0 instead of g_malloc.
(2) hvf TODO's in cpu.c explained: in-kernel irqchip.
(3) Introduce ins_len field in patch where actually used.
(4) Remove outdated comment "/* Definition of hvf_state is here */"
(5) Treat vcpu_dirty as boolean throughout.
(
This patch replaces the license header for those files that were either
GPL v2-or-v3, or GPL v2-only; the replacing license is GPL v2-or-later.
The code for task switching/handling, which is derived from KVM and
hence is GPL v2-only, is isolated in the new files (with this license)
x86_task.c/.h, a
This patch adds the function apic_get_highest_priority_irr to
apic.c and exports it through the interface in apic.h for use by hvf.
Signed-off-by: Sergio Andres Gomez Del Real
---
hw/intc/apic.c | 12
include/hw/i386/apic.h | 1 +
2 files changed, 13 insertions(+)
diff --g
This patch generalizes some code in cpu.c, sharing code and data between
hvf and kvm. It also begins calling the new hvf_get_supported_cpuid
where appropriate.
Signed-off-by: Sergio Andres Gomez Del Real
---
target/i386/cpu-qom.h | 4 +--
target/i386/cpu.c | 77 +
This patch adds to the configure script the code to support the
--enable-hvf argument. If the OS is Darwin, it checks for presence of
HVF in the system. The patch also adds strings related to HVF in the
file qemu-options.hx.
QEMU will only support the modern syntax style '-M accel=hvf' no enable
hv
This patch makes use of the helper functions for handling xsave in
xsave_helper.c, which are shared with kvm.
Signed-off-by: Sergio Andres Gomez Del Real
---
target/i386/hvf-utils/x86hvf.c | 63 ++
1 file changed, 8 insertions(+), 55 deletions(-)
diff --g
This patch injects a GP fault when the guest vmexit's by executing a
vmcall instruction.
Signed-off-by: Sergio Andres Gomez Del Real
---
target/i386/hvf-all.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/target/i386/hvf-all.c b/target/i386/hvf-all.c
index 105a63ad4f..0a
This patch implements setting the tracking of dirty vga pages, using hvf's
interface to protect guest memory. It uses the MemoryListener callback
mechanism through .log_start/stop/sync
Signed-off-by: Sergio Andres Gomez Del Real
---
include/sysemu/hvf.h | 5
target/i386/hvf-all.c | 74 +++
The files originally added from Google's repository in previous patches
won't compile cleanly unless some functions are implemented in cpus.c and some
other reorganization is done. This patch adds that code and does some
general refactoring in preparation for compiling in subsequent patches.
Signe
This patch adds to target/i386/Makefile.objs the necessary rules so
that the new files for hvf are compiled by the build system.
Signed-off-by: Sergio Andres Gomez Del Real
---
target/i386/Makefile.objs | 1 +
1 file changed, 1 insertion(+)
diff --git a/target/i386/Makefile.objs b/target/i386/M
QEMU currently aborts if you try to use the device at the command
line:
$ ppc64-softmmu/qemu-system-ppc64 -S -machine prep -device pc87312
Unexpected error in qemu_chr_fe_init() at chardev/char-fe.c:222:
qemu-system-ppc64: -device pc87312: Device 'parallel0' is in use
Aborted (core dumped)
It use
Currently before submitting a series, devs should run checkpatch.pl
across each patch to be submitted. This can be automated using a
command such as:
git rebase -i master -x 'git show | ./scripts/checkpatch.pl -'
This is rather long winded to type, so this patch introduces a way
to tell checkpa
** Bug watch removed: Virtualbox Trac #10532
http://www.virtualbox.org/ticket/10532
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/996798
Title:
Incorrect order of task switching
Status in QEMU:
The default cpu model on s390x does not provide zPCI, which is
not yet wired up on tcg. Moreover, virtio-ccw is the standard
on s390x, so use the -ccw instead of the -pci versions of virtio
devices on s390x.
Reviewed-by: Kevin Wolf
Signed-off-by: Cornelia Huck
---
tests/qemu-iotests/040 | 6 ++
This patch refactors the event-injection code for hvf by using the
appropriate fields already provided by CPUX86State. At vmexit, it fills
these fields so that hvf_inject_interrupts can just retrieve them without
calling into hvf.
Signed-off-by: Sergio Andres Gomez Del Real
---
target/i386/cpu.c
The default cpu model on s390x does not provide zPCI, which is
not yet wired up on tcg. Moreover, virtio-ccw is the standard
on s390x, so use the -ccw instead of the -pci versions of virtio
devices on s390x.
Signed-off-by: Cornelia Huck
---
tests/qemu-iotests/051| 12 +++-
tests/
This patch implements hvf_get_supported_cpuid, which returns the set of
features supported by both the host processor and the hypervisor.
Signed-off-by: Sergio Andres Gomez Del Real
---
target/i386/hvf-utils/x86_cpuid.c | 138 ++
1 file changed, 138 insertions
On 13.09.2017 11:10, Cornelia Huck wrote:
> The default cpu model on s390x does not provide zPCI, which is
> not yet wired up on tcg. Moreover, virtio-ccw is the standard
> on s390x.
>
> Using virtio-scsi will implicitly pick the right device, so just
> switch to that for simplicity.
>
> Signed-o
The default cpu model on s390x does not provide zPCI, which is
not yet wired up on tcg. Moreover, virtio-ccw is the standard
on s390x.
Using virtio-scsi will implicitly pick the right device, so just
switch to that for simplicity.
Signed-off-by: Cornelia Huck
---
tests/qemu-iotests/067 | 3
** Bug watch removed: Gentoo Bugzilla #431640
https://bugs.gentoo.org/show_bug.cgi?id=431640
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1037675
Title:
Guest Kernel Panic if using "-cpu host"
On 13.09.2017 11:10, Cornelia Huck wrote:
> The default cpu model on s390x does not provide zPCI, which is
> not yet wired up on tcg. Moreover, virtio-ccw is the standard
> on s390x, so use the -ccw instead of the -pci versions of virtio
> devices on s390x.
>
> Signed-off-by: Cornelia Huck
> ---
Hi Philippe,
All patches got Reviewed-by. Do you want me to change alias to remap and
send
v9 or wait so that you get time to review?
Thanks,
Sundeep
On Fri, Sep 8, 2017 at 12:56 PM, sundeep subbaraya
wrote:
> Hi Philippe,
>
> On Fri, Sep 8, 2017 at 3:08 AM, Philippe Mathieu-Daudé
> wrote:
>
Recent changes in s390x made pci support dependant on the zpci cpu
feature, which is not provided on all models (and not on by default).
This means we cannot instatiate pci devices on a standard qemu
invocation for s390x. Moreover, the zpci instructions are not even
wired up for tcg yet, so actuall
On Tue, 12 Sep 2017 19:19:56 +0200
Halil Pasic wrote:
> On 09/12/2017 05:59 PM, Cornelia Huck wrote:
> > On Tue, 12 Sep 2017 17:43:03 +0200
> > Halil Pasic wrote:
> >
> >> On 09/12/2017 04:37 PM, Cornelia Huck wrote:
> >>> On Mon, 11 Sep 2017 13:36:29 +0200
> >>> Halil Pasic wrote:
> >>>
Signed-off-by: Gerd Hoffmann
Reviewed-by: Fam Zheng
Reviewed-by: Thomas Huth
Tested-by: Thomas Huth
Message-id: 20170908111217.21985-3-kra...@redhat.com
---
hw/usb/Makefile.objs | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/hw/usb/Makefile.objs b/hw/usb/Makefile.objs
inde
From: Alexey Kardashevskiy
The existing XHCI code reads the Event Ring Segment Table Base Address
Register (ERSTBA) every time when it is changed. However zero is its
default state so one would think that zero there means it is not in use.
This adds a check for ERSTBA in addition to the existing
Nowdays we use libusb for usb-host, so we don't have different code
for linux vs. bsd any more. So there is little reason to have the
HOST_USB variable, we can just write things directly into the Makefile
and avoid a pointless indirection.
Signed-off-by: Gerd Hoffmann
Reviewed-by: Fam Zheng
Rev
From: Philippe Mathieu-Daudé
Signed-off-by: Philippe Mathieu-Daudé
Reviewed-by: Thomas Huth
Signed-off-by: Gerd Hoffmann
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 36eeb42d19..2c333aba21 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -99
It starts from a "make check" failure on one of my private tree. The
problem is that when we do "device_del" we normally looking for two
things: one response (which is mostly empty), and a REMOVE event. The
tricky point is the event can either be there before/after the empty
response. So I added
The following changes since commit 619c200f6ce2f44fbc8a5732174530c3b4782aab:
Merge remote-tracking branch 'remotes/mcayland/tags/qemu-openbios-signed'
into staging (2017-09-11 11:44:30 +0100)
are available in the git repository at:
git://git.kraxel.org/qemu tags/usb-20170913-pu
Device deletion is tricky since we'll get both a response and an event,
while the order of arrival may vary. Provide a helper to handle this
complexity.
Signed-off-by: Peter Xu
---
tests/libqtest.c | 48
tests/libqtest.h | 8
2 files ch
Signed-off-by: Peter Xu
---
tests/libqos/usb.c| 11 ++-
tests/usb-hcd-uhci-test.c | 14 +-
tests/usb-hcd-xhci-test.c | 29 ++---
3 files changed, 5 insertions(+), 49 deletions(-)
diff --git a/tests/libqos/usb.c b/tests/libqos/usb.c
index 0cdfae
Since we have qmp_device_del(), pair them up.
Signed-off-by: Peter Xu
---
tests/libqtest.c | 15 +++
tests/libqtest.h | 9 +
2 files changed, 24 insertions(+)
diff --git a/tests/libqtest.c b/tests/libqtest.c
index a34d8c4..c7da962 100644
--- a/tests/libqtest.c
+++ b/tests/l
Signed-off-by: Peter Xu
---
tests/libqos/pci.c| 15 +++
tests/libqos/usb.c| 17 -
tests/usb-hcd-uhci-test.c | 14 ++
tests/usb-hcd-xhci-test.c | 23 +++
4 files changed, 12 insertions(+), 57 deletions(-)
diff --git a/tes
Peter Xu wrote:
> On Tue, Aug 08, 2017 at 06:26:11PM +0200, Juan Quintela wrote:
>
> [...]
>
>> void migration_fd_process_incoming(QEMUFile *f)
>> {
>> -Coroutine *co = qemu_coroutine_create(process_incoming_migration_co, f);
>> -
>> +Coroutine *co = qemu_coroutine_create(process_incomin
no-reply writes:
> Hi,
> This series seems to have some coding style problems. See output below for
> more information:
> Subject: [Qemu-devel] [PATCH v5 00/22] instrument: Add basic event
> instrumentation
> Message-id: 150525010239.15988.8172586618197849619.st...@frigg.lan
> Type: series
> =
From: Pranavkumar Sawargaonkar
To implement INTx to gsi routing we need to pass the gpex host
bridge the gsi associated to each INTx index. Let's introduce
irq_num array and gpex_set_irq_num setter function.
Signed-off-by: Pranavkumar Sawargaonkar
Signed-off-by: Tushar Jagad
Signed-off-by: Eri
This series implements INTx to gsi routing for ARM VIRT/Gpex. This is
a respin of [1] which was lost in limbo.
ARM virt uses GPEX PCIe bridge. This latter does not implement INTx
to GSI routing. PCIe/INTx assignment works but the consequence is
irqfd is not used along with INTx interrupts and VFIO
From: Pranavkumar Sawargaonkar
Let's provide the GPEX host bridge with the INTx/gsi mapping. This is
needed for INTx/gsi routing.
Signed-off-by: Pranavkumar Sawargaonkar
Signed-off-by: Tushar Jagad
Signed-off-by: Eric Auger
Reviewed-by: Andrew Jones
Tested-by: Feng Kan
---
v3 -> v4:
- don
From: Pranavkumar Sawargaonkar
Now we are able to retrieve the gsi from the INTx pin, let's
enable intx_to_irq routing. From that point on, irqfd becomes
usable along with INTx when assigning a PCIe device.
Signed-off-by: Pranavkumar Sawargaonkar
Signed-off-by: Tushar Jagad
Signed-off-by: Eric
no-reply writes:
> Hi,
> This series failed automatic build test. Please find the testing commands and
> their output below. If you have docker installed, you can probably reproduce
> it
> locally.
> Subject: [Qemu-devel] [PATCH v5 00/22] instrument: Add basic event
> instrumentation
> Message
On 13.09.2017 11:36, Peter Xu wrote:
> It starts from a "make check" failure on one of my private tree. The
> problem is that when we do "device_del" we normally looking for two
> things: one response (which is mostly empty), and a REMOVE event. The
> tricky point is the event can either be there
On Mon, 11 Sep 2017 18:36:00 +0200
Halil Pasic wrote:
> On 09/06/2017 02:51 PM, Cornelia Huck wrote:
> +void ccw_dstream_init(CcwDataStream *cds, CCW1 const *ccw, ORB const
> *orb)
> +{
> +/*
> + * We don't support MIDA (an optional facility) yet and we
> +
"Daniel P. Berrange" wrote:
> On Tue, Aug 08, 2017 at 06:26:25PM +0200, Juan Quintela wrote:
>> We make the locking and the transfer of information specific, even if we
>> are still receiving things through the main thread.
>>
>> Signed-off-by: Juan Quintela
>>
>> --
>>
>> We split when we cre
This series adds an API to add instrumentation events.
It also provides additional APIs for:
* Controlling tracing events.
* Peek/poke guest memory.
TODO:
* Replace qi_event_gen_* with generating calls to arbitrary functions (e.g.,
qi_event_gen_call(num_args, va_list)).
* Flush all TBs when an
Signed-off-by: Lluís Vilanova
---
MAINTAINERS |6 ++
docs/instrument.txt | 173 +++
2 files changed, 179 insertions(+)
create mode 100644 docs/instrument.txt
diff --git a/MAINTAINERS b/MAINTAINERS
index 36eeb42d19..fb0eaee06a 100644
-
On Mon, 11 Sep 2017 20:08:16 +0200
Halil Pasic wrote:
> On 09/06/2017 03:10 PM, Cornelia Huck wrote:
> > On Tue, 5 Sep 2017 13:16:44 +0200
> > Halil Pasic wrote:
> >
> >> Let's add indirect data addressing support for our virtual channel
> >> subsystem. This implementation does no prefetchin
On Mon, 11 Sep 2017 20:14:59 +0200
Halil Pasic wrote:
> On 09/06/2017 02:42 PM, Cornelia Huck wrote:
> >> @@ -488,7 +446,8 @@ static int virtio_ccw_cb(SubchDev *sch, CCW1 ccw)
> >> } else {
> >> virtio_bus_get_vdev_config(&dev->bus, vdev->config);
> >> /* XXX co
On 13.09.2017 11:36, Peter Xu wrote:
> Since we have qmp_device_del(), pair them up.
>
> Signed-off-by: Peter Xu
> ---
> tests/libqtest.c | 15 +++
> tests/libqtest.h | 9 +
> 2 files changed, 24 insertions(+)
>
> diff --git a/tests/libqtest.c b/tests/libqtest.c
> index a34
Signed-off-by: Lluís Vilanova
---
configure |9 +
1 file changed, 9 insertions(+)
diff --git a/configure b/configure
index fd7e3a5e81..a21d1bceb9 100755
--- a/configure
+++ b/configure
@@ -356,6 +356,7 @@ pie=""
qom_cast_debug="yes"
trace_backends="log"
trace_file="trace"
+instrum
1 - 100 of 419 matches
Mail list logo
