Am 16.07.2014 00:21, schrieb Mark Cave-Ayland:
At the moment my work is focused on getting the basic system emulation
up and running, so I haven't spent much time looking at the graphics
side at all.
I have noticed that the kernel falls back to the dummy console during
boot, so perhaps it is una
On 07/15/2014 06:29 AM, Paolo Bonzini wrote:
> Il 14/07/2014 05:17, Alexey Kardashevskiy ha scritto:
>>> > No, you should politely bother them again.
>>
>> That does not seem helping though :-/
>
> Sorry. :)
>
> Well, patch 1 is the same as v6 and for the others Cornelia and Alex can
> ack it. I
Il 16/07/2014 19:10, Dr. David Alan Gilbert ha scritto:
> >
> >Handling it within the migration thread would make it much more complicated
> >(which would be bad since it's already complex enough);
>
> Ok. I'm not sure why it is more complicated since migration is essentially
> two-phase, one w
On 07/17/2014 11:43 AM, Wangkai (Kevin,C) wrote:
>
>> -Original Message-
>> From: Stefan Hajnoczi [mailto:stefa...@gmail.com]
>> Sent: Tuesday, July 15, 2014 11:00 PM
>> To: Wangkai (Kevin,C)
>> Cc: Stefan Hajnoczi; Lee yang; qemu-devel@nongnu.org;
>> aligu...@amazon.com
>> Subject: Re: [Qe
From: Hu Tao
This patch is to solve a problem that when you add a hot-pluggable memory,
you can't remove the memory.
Its approach is to set GPE status bit by qemu, then generate SCI to notify
guest os. Guest os checks device status, and free memory resource if possible,
then generate OST. Final
Cc: Eric Blake
Signed-off-by: Liu Yuan
---
qapi/block-core.json | 20 +++-
1 file changed, 19 insertions(+), 1 deletion(-)
diff --git a/qapi/block-core.json b/qapi/block-core.json
index e378653..42033d9 100644
--- a/qapi/block-core.json
+++ b/qapi/block-core.json
@@ -1384,6 +138
v4:
- swap the patch order
- update comment for fifo pattern in qaip
- use qapi enumeration in quorum driver instead of manual parsing
v3:
- separate patch into two, one for quorum and one for qapi for easier review
- add enumeration for quorum read pattern
- remove unrelated blank line fix
This patch adds single read pattern to quorum driver and quorum vote is default
pattern.
For now we do a quorum vote on all the reads, it is designed for unreliable
underlying storage such as non-redundant NFS to make sure data integrity at the
cost of the read performance.
For some use cases as
> -Original Message-
> From: Stefan Hajnoczi [mailto:stefa...@gmail.com]
> Sent: Tuesday, July 15, 2014 11:00 PM
> To: Wangkai (Kevin,C)
> Cc: Stefan Hajnoczi; Lee yang; qemu-devel@nongnu.org;
> aligu...@amazon.com
> Subject: Re: [Qemu-devel] [PATCH] Tap: fix vcpu long time io blocking
>
On Thu, Jul 17, 2014 at 1:05 AM, Alex Bennée wrote:
>
> Fabian Aggeler writes:
>
>> The SP810, which is present in the Versatile Express motherboards,
>> allows to set the timing reference to either REFCLK or TIMCLK.
>> QEMU currently sets the SP804 timer to 1MHz by default. To reflect
>> this, we
On Thu, Jul 17, 2014 at 12:42 AM, Fabian Aggeler wrote:
> This adds a device model for the PrimeXsys System Controller (SP810)
> which is present in the Versatile Express motherboards. It is
> so far read-only but allows to set the SCCTRL register.
>
> Signed-off-by: Fabian Aggeler
> ---
> defau
On Thu, Jul 17, 2014 at 1:48 AM, Yuanzhen Gu wrote:
> Thanks very much Andrey!
>
> how can I figure out whether fsfreeze not succeed while taking snapshot, if
> I run a simple application inside VM, say mysql? thanks!
>
> Best,
> Yuanzhen
>
>
> On Wed, Jul 16, 2014 at 5:25 PM, Andrey Korolyov wro
Thanks very much Andrey!
how can I figure out whether fsfreeze not succeed while taking snapshot, if
I run a simple application inside VM, say mysql? thanks!
Best,
Yuanzhen
On Wed, Jul 16, 2014 at 5:25 PM, Andrey Korolyov wrote:
> On Thu, Jul 17, 2014 at 1:18 AM, Eric Blake wrote:
> > On 07/
Thank you very much, Eric!
So do you mean, if I turn on libvirt debugging to trace QMP/agent commands,
I can find the pause and thaw functions in the source code, is it right ?
and is there any way that I freeze and thaw outside guest agent via command
line? or profiling tools suggest for freez
On Thu, Jul 17, 2014 at 1:28 AM, Marcin Gibuła wrote:
>> Tested on iscsi pool, though there are no-cache requirement and rbd
>> with disabled cache may survive one migration but iscsi backend hangs
>> always. As it was before, just rolling back problematic commit fixes
>> the problem and adding cp
Tested on iscsi pool, though there are no-cache requirement and rbd
with disabled cache may survive one migration but iscsi backend hangs
always. As it was before, just rolling back problematic commit fixes
the problem and adding cpu_synchronize_all_states to migration.c has
no difference at a gla
On Thu, Jul 17, 2014 at 1:18 AM, Eric Blake wrote:
> On 07/16/2014 03:13 PM, Yuanzhen Gu wrote:
>> Hi folks,
>>
>>
>> I am going to make a patch, and need to find the pause and thaw(restore)
>> function before and after taking Live QEMU Snapshot respectively.
>
> Libvirt has the ability to do just
On 07/16/2014 03:13 PM, Yuanzhen Gu wrote:
> Hi folks,
>
>
> I am going to make a patch, and need to find the pause and thaw(restore)
> function before and after taking Live QEMU Snapshot respectively.
Libvirt has the ability to do just that, when taking external disk-only
snapshots. You can tu
Hi folks,
I am going to make a patch, and need to find the pause and thaw(restore)
function before and after taking Live QEMU Snapshot respectively.
Basically, I'm using # (qemu) snapshot_blkdev
taking snapshot,
http://wiki.qemu.org/Features/Snapshotsmy profile tool didn't work when
givi
Hi,
could you please try adding hyperv to the vm options, as shown here:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1308341/comments/10
Please let us know if that helps.
** Changed in: qemu (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you ar
On 06/30/2014 10:00 AM, Matthew Rosato wrote:
> This patchset adds support in s390 for a pool of standby memory,
> which can be set online/offline by the guest (ie, via chmem).
> The standby pool of memory is allocated as the difference between
> the initial memory setting and the maxmem setting.
The fuzz submodule of the qcow2 image generator contains fuzzing functions for
image fields.
Each fuzzing function contains list of constraints and a call of a helper
function that randomly selects a fuzzed value satisfied to one of constraints.
For now constraints include only known as invalid or
The layout submodule of the qcow2 package creates a random valid image,
randomly selects some amount of its fields, fuzzes them and write the fuzzed
image to the file. Fuzzing process can be controlled by external configuration.
Now only a header, header extensions and a backing file name are gene
__init__.py provides the public API required by the test runner
Signed-off-by: Maria Kustova
---
tests/image-fuzzer/qcow2/__init__.py | 1 +
1 file changed, 1 insertion(+)
create mode 100644 tests/image-fuzzer/qcow2/__init__.py
diff --git a/tests/image-fuzzer/qcow2/__init__.py
b/tests/image-f
'Overall fuzzer requirements' chapter contains the current product vision and
features done and to be done. This chapter is still in progress.
Signed-off-by: Maria Kustova
---
tests/image-fuzzer/docs/image-fuzzer.txt | 239 +++
1 file changed, 239 insertions(+)
creat
The purpose of the test runner is to prepare test environment (e.g. create a
work directory, a test image, etc), execute the program under test with
parameters, indicate a test failure if the program was killed during test
execution and collect core dumps, logs and other test artifacts.
The test r
This patch series introduces the image fuzzer, a tool for stability and
reliability testing.
Its approach is to run large amount of tests in background. During every test a
program (e.g. qemu-img) is called to read or modify an invalid test image.
A test image has valid inner structure defined by i
** Changed in: qemu
Status: Invalid => Opinion
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1338563
Title:
README refers to a non-extant file
Status in QEMU:
Opinion
Bug description:
Am 16.07.2014 um 20:07 hat Eric Blake geschrieben:
> On 07/16/2014 09:48 AM, Kevin Wolf wrote:
> > @@ -1154,7 +1167,7 @@ void bdrv_set_backing_hd(BlockDriverState *bs,
> > BlockDriverState *backing_hd)
> > bdrv_op_unblock(bs->backing_hd, BLOCK_OP_TYPE_COMMIT,
> > bs->back
On Wed, Jul 16, 2014 at 5:24 PM, Andrey Korolyov wrote:
> On Wed, Jul 16, 2014 at 3:52 PM, Marcelo Tosatti wrote:
>> On Wed, Jul 16, 2014 at 12:38:51PM +0400, Andrey Korolyov wrote:
>>> On Wed, Jul 16, 2014 at 5:16 AM, Marcelo Tosatti
>>> wrote:
>>> > On Wed, Jul 16, 2014 at 03:40:47AM +0400, A
On 07/16/2014 09:48 AM, Kevin Wolf wrote:
> If qemu couldn't find out what O_DIRECT alignment to use with a given
> file, it would run into assert(bdrv_opt_mem_align(bs) != 0); in block.c
> and confuse users. This adds a more descriptive error message for such
> cases.
>
> Signed-off-by: Kevin Wol
On 07/16/2014 09:48 AM, Kevin Wolf wrote:
> Signed-off-by: Kevin Wolf
> ---
> block.c | 33 +++--
> block/iscsi.c | 3 +--
> block/qcow2.c | 4 +---
> block/qed.c | 4 +---
> block/raw-posix.c | 4 +---
Am 16.07.2014 18:46, schrieb Peter Maydell:
> On 16 July 2014 17:28, Stefan Weil wrote:
>> a recent commit (e49ab19fcaa617ad6cdfe1ac401327326b6a2552) increased the
>> requirements for libiscsi from 1.4.0 to 1.9.0. From a user's point of
>> view, this change results in a regression for Debian and s
Am 16.07.2014 19:23, schrieb ronnie sahlberg:
> On Wed, Jul 16, 2014 at 10:11 AM, Stefan Weil wrote:
>> Am 16.07.2014 18:49, schrieb Paolo Bonzini:
>>> Il 16/07/2014 18:28, Stefan Weil ha scritto:
Debian testing includes a brand new libiscsi, but it
does not include libiscsi.pc, so pkg-c
16.07.2014 21:23, ronnie sahlberg wrote:
> If you ask debian to upgrade. Could you ask them to wait and upgrade after I
> have release the next version, hopefully if all goes well, at the end
> of this week?
There's no problem in updating now to fix missing .pc file and to update
next week to inc
16.07.2014 21:11, Stefan Weil wrote:
> Am 16.07.2014 18:49, schrieb Paolo Bonzini:
>> Il 16/07/2014 18:28, Stefan Weil ha scritto:
>>> Debian testing includes a brand new libiscsi, but it
>>> does not include libiscsi.pc, so pkg-config won't know that it is
>>> available and configure will disable
On Wed, Jul 16, 2014 at 10:11 AM, Stefan Weil wrote:
> Am 16.07.2014 18:49, schrieb Paolo Bonzini:
>> Il 16/07/2014 18:28, Stefan Weil ha scritto:
>>> Debian testing includes a brand new libiscsi, but it
>>> does not include libiscsi.pc, so pkg-config won't know that it is
>>> available and config
Am 16.07.2014 18:49, schrieb Paolo Bonzini:
> Il 16/07/2014 18:28, Stefan Weil ha scritto:
>> Debian testing includes a brand new libiscsi, but it
>> does not include libiscsi.pc, so pkg-config won't know that it is
>> available and configure will disable libiscsi.
>
> That's a packaging bug.
CC'
* Paolo Bonzini (pbonz...@redhat.com) wrote:
> Il 16/07/2014 13:52, Dr. David Alan Gilbert ha scritto:
> >* Paolo Bonzini (pbonz...@redhat.com) wrote:
> >>Il 16/07/2014 11:37, Dr. David Alan Gilbert ha scritto:
> >
> >+
> >+/* If it's already open, return it */
> >+if (qfs->
Il 16/07/2014 18:28, Stefan Weil ha scritto:
Debian testing includes a brand new libiscsi, but it
does not include libiscsi.pc, so pkg-config won't know that it is
available and configure will disable libiscsi.
That's a packaging bug.
I have a patch which
fixes this, so QEMU for Debian testin
On 16 July 2014 17:28, Stefan Weil wrote:
> a recent commit (e49ab19fcaa617ad6cdfe1ac401327326b6a2552) increased the
> requirements for libiscsi from 1.4.0 to 1.9.0. From a user's point of
> view, this change results in a regression for Debian and similar Linux
> distributions: QEMU no longer incl
This patch introduces the parameter of 'num_queues', and
prepare for supporting mutli vqs of virtio-blk.
Signed-off-by: Ming Lei
---
hw/block/virtio-blk.c |1 +
include/hw/virtio/virtio-blk.h |1 +
2 files changed, 2 insertions(+)
diff --git a/hw/block/virtio-blk.c b/hw/block/v
This patch increases max event to 256 for the comming
virtio-blk multi virtqueue support.
Signed-off-by: Ming Lei
---
block/linux-aio.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/block/linux-aio.c b/block/linux-aio.c
index 5eb9c92..c06a57d 100644
--- a/block/linux-aio
g_slice_new(VirtIOBlockReq), its free pair and access the instance
is a bit slow since sizeof(VirtIOBlockReq) takes more than 40KB,
so use object pool to speed up its allocation and release.
With this patch, ~20% thoughput improvement can
be observed in my laptop based VM test, and ~5%
improvement
This patch introduces object allocation pool for speeding up
object allocation in fast path.
Signed-off-by: Ming Lei
---
include/qemu/obj_pool.h | 64 +++
1 file changed, 64 insertions(+)
create mode 100644 include/qemu/obj_pool.h
diff --git a/incl
Now we only support multi vqs for dataplane case.
Signed-off-by: Ming Lei
---
hw/block/virtio-blk.c | 16 +++-
include/hw/virtio/virtio-blk.h |3 +++
2 files changed, 18 insertions(+), 1 deletion(-)
diff --git a/hw/block/virtio-blk.c b/hw/block/virtio-blk.c
index ab99
This patch enables selective bypassing for the
coroutine in bdrv_co_aio_rw_vector() if the image
format is raw.
With this patch, ~16% thoughput improvement can
be observed in my laptop based VM test, and ~7%
improvement is observed in the VM based on server.
Signed-off-by: Ming Lei
---
hw/block
Prepare for supporting mutli vqs per virtio-blk device.
Signed-off-by: Ming Lei
---
include/hw/virtio/virtio-blk.h |8
1 file changed, 8 insertions(+)
diff --git a/include/hw/virtio/virtio-blk.h b/include/hw/virtio/virtio-blk.h
index 45f8894..ad70c9a 100644
--- a/include/hw/virtio/
This reverts commit 76ef2cf5493a215efc351f48ae7094d6c183fcac.
Reintroduce the helper of raw_get_aio_fd() for enabling
coroutinue bypass mode in case of raw image.
Signed-off-by: Ming Lei
---
block/raw-posix.c | 34 ++
include/block/block.h |9 +
In the enqueue path, we can't complete request, otherwise
"Co-routine re-entered recursively" may be caused, so this
patch fixes the issue with below ideas:
- for -EAGAIN or partial completion, retry the submission by
an introduced event handler
- for part of completion, al
If device thinks that it isn't necessary to apply coroutine
in its performance sensitive path, it can call
qemu_aio_set_bypass_co(false) to bypass the coroutine which
has supported bypass mode and just call the function directly.
One example is virtio-blk dataplane.
Signed-off-by: Ming Lei
---
This patch supports to handle host notify from multi
virt queues, but still process/submit io in the
one iothread.
Currently this patch brings up below improvement
with two virtqueues(against single virtqueue):
---
|
No one uses the 'node' field any more, so remove it
from 'struct qemu_laiocb', and this can save 16byte
for the struct on 64bit arch.
Signed-off-by: Ming Lei
---
block/linux-aio.c |1 -
1 file changed, 1 deletion(-)
diff --git a/block/linux-aio.c b/block/linux-aio.c
index c06a57d..337f879 1
This patch introduces several APIs for supporting bypass qemu coroutine
in case of being not necessary and for performance's sake.
Signed-off-by: Ming Lei
---
include/block/coroutine.h |7 +++
include/block/coroutine_int.h |5 +
qemu-coroutine-lock.c |4 ++--
qemu
This patch adds bypass mode support for the coroutinue
in bdrv_co_aio_rw_vector(), which is in the fast path
of lots of block device, especially for virtio-blk dataplane.
Signed-off-by: Ming Lei
---
block.c | 129 +++
1 file changed, 1
Hi,
These patches bring up below 4 changes:
- introduce selective coroutine bypass mechanism
for improving performance of virtio-blk dataplane with
raw format image
- introduce object allocation pool and apply it to
virtio-blk dataplane for improving its p
Am 16.07.2014 02:26, schrieb Michael Roth:
> Hello,
>
> On behalf of the QEMU Team, I'd like to announce the availability of the
> third release candidate for the QEMU 2.1 release. This release is meant
> for testing purposes and should not be used in a production environment.
>
> http://wiki.qe
Il 16/07/2014 17:52, Andy Lutomirski ha scritto:
This updates x86's kvm_para.h for the feature bit definition and
target-i386/cpu.c for the feature name and default.
Signed-off-by: Andy Lutomirski
Thanks, looks good---assuming the kernel side will make it into 3.17,
I'll sync the headers onc
On Wed, Jul 16, 2014 at 09:36:23AM +0100, Peter Maydell wrote:
> On 16 July 2014 05:02, Rich Felker wrote:
> > The qemu-microblaze definition of struct stat64 seems to mismatch the
> > kernel definition, which is using asm-generic/stat.h. See:
> >
> > http://git.qemu.org/?p=qemu.git;a=blob;f=linux
This updates x86's kvm_para.h for the feature bit definition and
target-i386/cpu.c for the feature name and default.
Signed-off-by: Andy Lutomirski
---
linux-headers/asm-x86/kvm_para.h | 2 ++
target-i386/cpu.c| 5 +++--
2 files changed, 5 insertions(+), 2 deletions(-)
diff --gi
If qemu couldn't find out what O_DIRECT alignment to use with a given
file, it would run into assert(bdrv_opt_mem_align(bs) != 0); in block.c
and confuse users. This adds a more descriptive error message for such
cases.
Signed-off-by: Kevin Wolf
---
block/raw-posix.c | 35 +++
Signed-off-by: Kevin Wolf
---
block.c | 33 +++--
block/iscsi.c | 3 +--
block/qcow2.c | 4 +---
block/qed.c | 4 +---
block/raw-posix.c | 4 +---
block/raw_bsd.c | 3 +--
block/stream.c
Kevin Wolf (2):
block: Add Error argument to bdrv_refresh_limits()
raw-posix: Fail gracefully if no working alignment is found
block.c | 33 +++--
block/iscsi.c | 3 +--
block/qcow2.c | 4 +---
block/qed.c |
Fabian Aggeler writes:
> The SP810, which is present in the Versatile Express motherboards,
> allows to set the timing reference to either REFCLK or TIMCLK.
> QEMU currently sets the SP804 timer to 1MHz by default. To reflect
> this, we set the TimerEn0Sel, TimerEn1Sel, TimerEn2Sel, and
> TimerEn
The SP810, which is present in the Versatile Express motherboards,
allows to set the timing reference to either REFCLK or TIMCLK.
QEMU currently sets the SP804 timer to 1MHz by default. To reflect
this, we set the TimerEn0Sel, TimerEn1Sel, TimerEn2Sel, and
TimerEn3Sel of the system control register
This adds a device model for the PrimeXsys System Controller (SP810)
which is present in the Versatile Express motherboards. It is
so far read-only but allows to set the SCCTRL register.
Signed-off-by: Fabian Aggeler
---
default-configs/arm-softmmu.mak | 1 +
hw/misc/Makefile.objs |
Hi,
The Versatile Express emulation in QEMU currently does not
have a model of the SP810 used in real hardware. The registers
provided by this System Controller can be used to set the
frequency of the SP804 timers. On newer releases of the board
the SP804 is set to 32kHz by default and has to be i
On Thu, Jul 03, 2014 at 11:27:40PM +0300, Michael S. Tsirkin wrote:
> On Thu, Jul 03, 2014 at 12:09:28PM -0700, Jesse Barnes wrote:
> > On Thu, 3 Jul 2014 14:26:12 -0400
> > Konrad Rzeszutek Wilk wrote:
> >
> > > On Thu, Jul 03, 2014 at 10:32:12AM +0300, Michael S. Tsirkin wrote:
> > > > On Wed,
Public bug reported:
Windows 95 (first version, not 95A or OSR2) setup hangs on QEMU version 2.0.0.
It was compiled from the sources on Fedora 20.
Setup starts without problems, it goes through the first phase and then hangs
on the "Getting ready to run Windows 95 for the first time..." screen
On Wed, 16 Jul 2014 14:18:00 +0200
Sebastian Tanase wrote:
> The icount option already implemented in QEMU allows the guest to run at a
> theoretical
> frequency of 1/(2^N) GHz (N is the icount parameter). The goal of this patch
> is to have a
> real guest frequency close to the one imposed by
On Wed, Jul 16, 2014 at 3:52 PM, Marcelo Tosatti wrote:
> On Wed, Jul 16, 2014 at 12:38:51PM +0400, Andrey Korolyov wrote:
>> On Wed, Jul 16, 2014 at 5:16 AM, Marcelo Tosatti wrote:
>> > On Wed, Jul 16, 2014 at 03:40:47AM +0400, Andrey Korolyov wrote:
>> >> On Wed, Jul 16, 2014 at 2:01 AM, Paolo
Il 16/07/2014 14:18, Sebastian Tanase ha scritto:
v3 -> v4
* Add better error handling for 'strtol' in patch 2
* Add 'Sleep' instead of 'nanosleep' for Windows hosts in patch 4
* Remove function pointers from patches 4 and 5
Hi Sebastian, I think we're getting really close.
I asked a question
Il 16/07/2014 14:18, Sebastian Tanase ha scritto:
-static int64_t clocks_offset;
-if (!icount_align_option) {
-return;
+static int64_t realtime_clock_value;
Does this really need to be static?
+if (icount_align_option || !realtime_clock_value) {
+realtime_clock
Enable passthrough of vendor-specific commands.
Signed-off-by: Paolo Bonzini
---
hw/scsi/virtio-scsi.c | 24
1 file changed, 24 insertions(+)
diff --git a/hw/scsi/virtio-scsi.c b/hw/scsi/virtio-scsi.c
index 0eb069a..e8f4c0c 100644
--- a/hw/scsi/virtio-scsi.c
+++ b/hw/sc
The callback lets the bus provide the direction and transfer count
for passthrough commands, enabling passthrough of vendor-specific
commands.
Signed-off-by: Paolo Bonzini
---
hw/scsi/scsi-bus.c | 3 +--
hw/scsi/scsi-disk.c| 14 ++
hw/scsi/scsi-generic.c | 7 +++
includ
The per-SCSIDevice parse_cdb callback must not be called if the
request will go through special SCSIReqOps, so detect the special
cases early enough.
Signed-off-by: Paolo Bonzini
---
hw/scsi/scsi-bus.c | 44 +---
1 file changed, 25 insertions(+), 19 deleti
These callbacks will let devices do their own request parsing, or
defer it to the bus. If the bus does not provide an implementation,
in turn, fall back to the default parsing routine.
Swap the first two arguments to scsi_req_parse, and rename it to
scsi_req_parse_cdb, for consistency.
Signed-of
Public bug reported:
qemu-io and qemu-img fails with an assertion (see below) at attempt to
interact with the qcow2 image having large values in the 'incompatible
features' header field.
util/error.c:34: error_set: Assertion `*errp == ((void *)0)' failed.
The backtrace file and the test imag
This will be used for both scsi_block_new_request and the scsi-block
implementation of parse_cdb.
Signed-off-by: Paolo Bonzini
---
hw/scsi/scsi-disk.c | 38 ++
1 file changed, 26 insertions(+), 12 deletions(-)
diff --git a/hw/scsi/scsi-disk.c b/hw/scsi/scsi-d
Right now scsi-generic is parsing the CDB, in order to compute
the expected number of bytes to be transferred. This is necessary
if DMA is done by the HBA via scsi_req_data, but it prevents executing
vendor-specific commands via scsi-generic because we don't know how
to parse them.
If DMA is dele
Il 16/07/2014 13:52, Dr. David Alan Gilbert ha scritto:
* Paolo Bonzini (pbonz...@redhat.com) wrote:
Il 16/07/2014 11:37, Dr. David Alan Gilbert ha scritto:
+
+/* If it's already open, return it */
+if (qfs->file->return_path) {
+return qfs->file->return_path;
Wouldn't this l
The icount option already implemented in QEMU allows the guest to run at a
theoretical
frequency of 1/(2^N) GHz (N is the icount parameter). The goal of this patch is
to have a
real guest frequency close to the one imposed by using the icount option.
The main idea behind the algorithm is that we
Show in 'info jit' the current delay between the host clock
and the guest clock. In addition, print the maximum advance
and delay of the guest compared to the host.
Signed-off-by: Sebastian Tanase
Tested-by: Camille Bégué
---
cpu-exec.c| 19 ++-
cpus.c
The align option is used for activating the align algorithm
in order to synchronise the host clock and the guest clock.
Signed-off-by: Sebastian Tanase
Tested-by: Camille Bégué
---
cpus.c| 19 ---
include/qemu-common.h | 1 +
qemu-options.hx | 15 +
If the align option is enabled, we print to the user whenever
the guest clock is behind the host clock in order for he/she
to have a hint about the actual performance. The maximum
print interval is 2s and we limit the number of messages to 100.
If desired, this can be changed in cpu-exec.c
Signed-
The goal is to sleep qemu whenever the guest clock
is in advance compared to the host clock (we use
the monotonic clocks). The amount of time to sleep
is calculated in the execution loop in cpu_exec.
At first, we tried to approximate at each for loop the real time elapsed
while searching for a TB
Make icount parameter use QemuOpts style options in order
to easily add other suboptions.
Signed-off-by: Sebastian Tanase
Tested-by: Camille Bégué
Signed-off-by: Paolo Bonzini
---
cpus.c| 10 +-
include/qemu-common.h | 3 ++-
qemu-options.hx | 4 ++--
qtest.c
icount_time_shift is used for calculting the delay
qemu has to sleep in order to synchronise the
host and guest clocks. Therefore, we need it in
cpu-exec.c.
Signed-off-by: Sebastian Tanase
Tested-by: Camille Bégué
Signed-off-by: Paolo Bonzini
---
cpus.c| 8 ++--
include/qem
On 16 July 2014 10:17, Alex Bennée wrote:
> On aarch64 we do:
>
> #define unsupported_encoding(s, insn)\
> do { \
> qemu_log_mask(LOG_UNIMP, \
>
On Wed, Jul 16, 2014 at 09:35:16AM +0200, Marcin Gibuła wrote:
> >Andrey,
> >
> >Can you please provide instructions on how to create reproducible
> >environment?
> >
> >The following patch is equivalent to the original patch, for
> >the purposes of fixing the kvmclock problem.
> >
> >Perhaps it be
On Wed, Jul 16, 2014 at 12:38:51PM +0400, Andrey Korolyov wrote:
> On Wed, Jul 16, 2014 at 5:16 AM, Marcelo Tosatti wrote:
> > On Wed, Jul 16, 2014 at 03:40:47AM +0400, Andrey Korolyov wrote:
> >> On Wed, Jul 16, 2014 at 2:01 AM, Paolo Bonzini wrote:
> >> > Il 15/07/2014 23:25, Andrey Korolyov ha
* Paolo Bonzini (pbonz...@redhat.com) wrote:
> Il 16/07/2014 11:37, Dr. David Alan Gilbert ha scritto:
> >>>
> >>>+
> >>>+/* If it's already open, return it */
> >>>+if (qfs->file->return_path) {
> >>>+return qfs->file->return_path;
> >>
> >>Wouldn't this leave a dangling file descr
Riku Voipio wrote on 2014/07/16 08:54:45:
>
> On Tue, Jul 15, 2014 at 05:11:48PM +0200, Joakim Tjernlund wrote:
> > Riku Voipio wrote on 2014/07/15 16:12:26:
> > > On Mon, Jul 14, 2014 at 05:38:49PM +0200, Joakim Tjernlund wrote:
> > > > Alexander Graf wrote on 2014/07/14 17:21:33:
> > > > > On
Before adding new ports to VirtIOSerial devices, check if there's a
conflict in the 'name' parameter. This ensures two virtserialports with
identical names are not initialized.
Reported-by:
Signed-off-by: Amit Shah
---
hw/char/virtio-serial-bus.c | 22 ++
1 file changed, 22
To ensure two virtserialports don't get added to the system with the
same 'name' parameter, we need to access all the ports on all the
devices added, and compare the names.
We currently don't have a list of all VirtIOSerial devices added to the
system. This commit adds a simple linked list in whi
Hi,
The 2nd patch prevents adding ports to the system with conflicts in
the 'name' parameter. This is done by going through all the ports in
the system, including ports on other virtio-serial devices.
The first patch prepares for this by creating a linked list of all
available virtio-serial devi
This is not a bug. What happens is that QEMU echoes the command you
type onto the PTY. If you do not do a "cat /dev/pts/8", the PTY's buffer
gets full and QEMU stops reading from the PTY until it is emptied.
It doesn't happen if you use QMP.
** Changed in: qemu
Status: New => Invalid
--
> -Original Message-
> From: Stefan Hajnoczi [mailto:stefa...@gmail.com]
> Sent: Tuesday, July 15, 2014 11:00 PM
> To: Wangkai (Kevin,C)
> Cc: Stefan Hajnoczi; Lee yang; qemu-devel@nongnu.org;
> aligu...@amazon.com
> Subject: Re: [Qemu-devel] [PATCH] Tap: fix vcpu long time io blocking
>
Il 16/07/2014 11:37, Dr. David Alan Gilbert ha scritto:
+
+/* If it's already open, return it */
+if (qfs->file->return_path) {
+return qfs->file->return_path;
Wouldn't this leave a dangling file descriptor if you call
socket_dup_return_path twice, and then close the original Q
* Paolo Bonzini (pbonz...@redhat.com) wrote:
> Il 04/07/2014 19:41, Dr. David Alan Gilbert (git) ha scritto:
> >From: "Dr. David Alan Gilbert"
> >
> >Postcopy needs a method to send messages from the destination back to
> >the source, this is the 'return path'.
> >
> >+/* Give a QEMUFile* off t
1 - 100 of 118 matches
Mail list logo
