Gonglei writes:
> On 2015/2/2 17:37, Markus Armbruster wrote:
>
>> Gonglei writes:
>>
>>> On 2015/1/30 20:32, Markus Armbruster wrote:
>>>
Gonglei writes:
> On 2015/1/30 20:01, Markus Armbruster wrote:
>
>> Gonglei writes:
>>
>>> On 2015/1/30 15:46, Markus Armbru
On 02/02/15 23:46, Denis V. Lunev wrote:
On 02/02/15 23:40, Peter Lieven wrote:
Am 02.02.2015 um 21:09 schrieb Denis V. Lunev:
qemu_gluster_co_discard calculates size to discard as follows
size_t size = nb_sectors * BDRV_SECTOR_SIZE;
ret = glfs_discard_async(s->fd, offset, size,
&glu
> -Origin email-
> From: Max Filippov
> Sent Time: Tuesday, February 3, 2015
> To: Kaiyuan
> Cc: qemu-devel
> Subject: Re: [Qemu-devel] "Program received signal SIGUSR1" while debugging
> Qemu
>
> On Tue, Feb 3, 2015 at 8:28 AM, Kaiyuan wrote:
> > Hello, guys
> >
> > I am trying to us
> From: Paolo Bonzini [mailto:paolo.bonz...@gmail.com] On Behalf Of Paolo
> Bonzini
> On 22/01/2015 09:51, Pavel Dovgalyuk wrote:
> > These patches include only core function of the replay,
> > excluding the support for replaying serial, audio, network, and USB devices'
> > operations. Reverse deb
On Tue, Feb 3, 2015 at 8:28 AM, Kaiyuan wrote:
> Hello, guys
>
> I am trying to use gdb to debug qemu-system-ppc to see the details of tcg.
> However, after setting breakpoint in
> translate.c:gen_intermediate_code_internal and steps over, gdb showed
> message:
>
> Program received signal SIGUSR1,
qemu currently implements the hypercalls H_LOGICAL_CI_LOAD and
H_LOGICAL_CI_STORE as PAPR extensions. These are used by the SLOF firmware
for IO, because performing cache inhibited MMIO accesses with the MMU off
(real mode) is very awkward on POWER.
This approach breaks when SLOF needs to access
Hello, guys
I am trying to use gdb to debug qemu-system-ppc to see the details of tcg.
However, after setting breakpoint in translate.c:gen_intermediate_code_internal
and steps over, gdb showed message:
Program received signal SIGUSR1, User defined signal 1.
Then gdb jumped to cpus.c:642
Sorry, I find that the patch of "virtio-scsi: Optimize virtio_scsi_init_req"
can slove this problem.
By the way, can you tell me the reason of the change about cdb and sense?
On 2015-2-3 10:31, Wangting (Kathy) wrote:
> Hi Paolo,
>
> Recently I test IO performance with virtio-scsi, and find out
Hi Paolo,
Recently I test IO performance with virtio-scsi, and find out that the patch of
"virtio-scsi: add support for the any_layout feature" affects IO performance of
model
with 4KB 32iodepth sequence read.
Why cdb and sense is removed from the struct of VirtIOSCSICmdReq and
VirtIOSCSICmdRes
From: Christian Svensson
This patch adds support for atomic locks and is an adaption from
https://github.com/bluecmd/or1k-qemu/commits/or32-optimize
Tested via the atomic lock implementation of musl
Signed-off-by: Christian Svensson
Signed-off-by: Sebastian Macke
Reviwed-by: Jia Liu
Signed-o
From: Sebastian Macke
This patch separates the load and store instruction to a
separate function.
The repetition of the source code can be reduced and further
optimizations can be implemented.
In this case it checks for a zero offset and optimizes it.
Signed-off-by: Sebastian Macke
Reviwed-by:
Hi Anthony,
This is my OpenRISC patch queue for 2.3, it have been well tested, please pull.
Thanks to Christian and Sebastian, they made the LD/ST updated.
Regards,
Jia
The following changes since commit 16017c48547960539fcadb1f91d252124f442482:
softfloat: Clarify license status (2015-01-
On 2015/2/2 17:37, Markus Armbruster wrote:
> Gonglei writes:
>
>> On 2015/1/30 20:32, Markus Armbruster wrote:
>>
>>> Gonglei writes:
>>>
On 2015/1/30 20:01, Markus Armbruster wrote:
> Gonglei writes:
>
>> On 2015/1/30 15:46, Markus Armbruster wrote:
>>
>>> Gongl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/02/2015 05:37 PM, David Gibson wrote:
> On Thu, Jan 29, 2015 at 08:27:19PM +1100, Alexey Kardashevskiy wrote:
>> Every sPAPRTCETable object holds an IOMMU memory region which holds
>> a referenced to the sPAPRTCETable instance. So if we want to
On Mon, 02/02 20:34, Paolo Bonzini wrote:
>
>
> On 13/01/2015 09:53, Fam Zheng wrote:
> > We have module build support around for a while, but also had it bitrot
> > several times. It probably makes sense to enable it by default so that
> > people can notice and use it.
> >
> > Counterpart to --
On 01/30/15 17:32, Eric Blake wrote:
> On 01/30/2015 02:06 PM, Don Slutz wrote:
>> This adds two new inject commands:
>>
>> inject-vmport-reboot
>> inject-vmport-halt
>>
>> And three guest info commands:
>>
>> vmport-guestinfo-set
>> vmport-guestinfo-get
>> query-vmport-guestinfo
>>
>> More details
On 2015/2/2 20:54, Ian Jackson wrote:
Wei Liu writes ("Re: [v2][PATCH] libxl: add one machine property to support IGD GFX
passthrough"):
On Mon, Feb 02, 2015 at 09:17:23AM +0800, Tiejun Chen wrote:
When we're working to support IGD GFX passthrough with qemu
upstream, instead of "-gfx_passthr
On 2015/2/2 20:19, Wei Liu wrote:
On Mon, Feb 02, 2015 at 09:17:23AM +0800, Tiejun Chen wrote:
When we're working to support IGD GFX passthrough with qemu
upstream, instead of "-gfx_passthru" we'd like to make that
a machine option, "-machine xxx,-igd-passthru=on". This need
to bring a change o
On 2015/2/2 19:08, Ian Campbell wrote:
On Mon, 2015-02-02 at 09:17 +0800, Tiejun Chen wrote:
When we're working to support IGD GFX passthrough with qemu
upstream, instead of "-gfx_passthru" we'd like to make that
a machine option, "-machine xxx,-igd-passthru=on". This need
to bring a change on
On 02/02/2015 05:10 AM, Markus Armbruster wrote:
Kevin Wolf writes:
Am 30.01.2015 um 18:04 hat John Snow geschrieben:
On 01/30/2015 09:32 AM, Kevin Wolf wrote:
Am 21.01.2015 um 10:34 hat Markus Armbruster geschrieben:
I'm afraid I forgot much of the discussion we had before the break, a
The qemu process does not always need to be killed, just waiting for it
can be fine, too. This introduces a way to do so.
Signed-off-by: Max Reitz
---
tests/qemu-iotests/common.qemu | 12 +++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/tests/qemu-iotests/common.qemu b/
When the drive-mirror block job is completed, it will call bdrv_swap()
on the source and the target BDS; this should obviously not result in a
segmentation fault.
Signed-off-by: Max Reitz
---
tests/qemu-iotests/094 | 81 ++
tests/qemu-iotests/094.o
Right now, bdrv_swap() on NBD BDSs results in a segmentation fault
pretty much all of the time. This series fixes this.
Note that this is not a common case, as bdrv_swap() is generally only
performed on root BDSs (there are exceptions, though) and NBD BDSs
normally have a format BDS above them. Ho
Before this patch, the "opaque" pointer in an NBD BDS points to a
BDRVNBDState, which contains an NbdClientSession object, which in turn
contains a pointer to the BDS. This pointer may become invalid due to
bdrv_swap(), so drop it, and instead pass the BDS directly to the
nbd-client.c functions whi
On 02/02/2015 12:31 PM, Peter Maydell wrote:
> -void float_raise( int8 flags STATUS_PARAM )
> +void float_raise(int8 flags , float_status *status)
Extra space before comma.
r~
On 02/02/2015 12:31 PM, Peter Maydell wrote:
> Peter Maydell (3):
> softfloat: Expand out the STATUS_PARAM macro
> softfloat: expand out STATUS_VAR
> softfloat: expand out STATUS macro
>
> fpu/softfloat-specialize.h | 124 ++--
> fpu/softfloat.c| 1609
> +++
On 02/02/2015 05:25 AM, Paolo Bonzini wrote:
On 30/01/2015 19:41, John Snow wrote:
+/* Construct our Command Header (set_command_header handles endianness.) */
+memset(&cmd, 0x00, sizeof(cmd));
+cmd.flags = 5; /* reg_h2d_fis is 5 double-words long */
+cmd.flags = 0x400; /
On 02/02/2015 05:37 AM, Paolo Bonzini wrote:
On 30/01/2015 19:42, John Snow wrote:
+/**
+ * Boot and fully enable the HBA device.
+ * @see ahci_boot, ahci_pci_enable and ahci_hba_enable.
+ */
+static AHCIQState *ahci_macro_bootup(void)
Ugly name... I would just leave out this patch.
Paol
On 02/02/2015 05:35 AM, Paolo Bonzini wrote:
On 30/01/2015 19:42, John Snow wrote:
+void ahci_command_set_sizes(AHCICommand *cmd, uint64_t xbytes,
+unsigned prd_size)
+{
+/* Each PRD can describe up to 4MiB, and must not be odd. */
+g_assert_cmphex(prd_siz
On 01/29/2015 10:55 AM, Peter Maydell wrote:
> Support guest CPUs which need 7 MMU index values.
> Add a comment about what would be required to raise the limit
> further (trivial for 8, TCG backend rework for 9 or more).
>
> Signed-off-by: Peter Maydell
> Reviewed-by: Greg Bellows
> ---
> incl
On 02/02/15 23:40, Peter Lieven wrote:
Am 02.02.2015 um 21:09 schrieb Denis V. Lunev:
qemu_gluster_co_discard calculates size to discard as follows
size_t size = nb_sectors * BDRV_SECTOR_SIZE;
ret = glfs_discard_async(s->fd, offset, size, &gluster_finish_aiocb, acb);
glfs_discard_asyn
Am 02.02.2015 um 21:09 schrieb Denis V. Lunev:
> qemu_gluster_co_discard calculates size to discard as follows
> size_t size = nb_sectors * BDRV_SECTOR_SIZE;
> ret = glfs_discard_async(s->fd, offset, size, &gluster_finish_aiocb, acb);
>
> glfs_discard_async is declared as follows:
> int g
On 02/02/2015 05:27 AM, Paolo Bonzini wrote:
On 30/01/2015 19:41, John Snow wrote:
+/* Set the #cx'th command of port #px. */
+void ahci_set_command_header(AHCIQState *ahci, uint8_t px,
+ uint8_t cx, AHCICommandHeader *cmd)
+{
+uint64_t ba = ahci->port[px].clb
On Wed, 2015-01-28 at 16:37 +0800, Chen Fan wrote:
> when vfio device support FLR, then when device reset,
> we call VFIO_DEVICE_RESET ioctl to reset the device first,
> at kernel side, we also can see the order of reset:
> 3330 rc = pcie_flr(dev, probe);
> 3331 if (rc != -ENOTTY)
>
This patchset expands out all the uses of the softfloat STATUS_VAR,
STATUS_PARAM and STATUS macros and removes their definitions.
In my opinion these macros are basically just obfuscating the
passing around and use of a float_status pointer in the softfloat
code, and serve no useful purpose. I use
Expand out STATUS_PARAM wherever it is used and delete the definition.
Signed-off-by: Peter Maydell
---
fpu/softfloat-specialize.h | 50 +++---
fpu/softfloat.c| 387 -
include/fpu/softfloat.h| 332 +++---
Expand out and remove the STATUS_VAR macro.
Signed-off-by: Peter Maydell
---
fpu/softfloat-specialize.h | 50 ++-
fpu/softfloat.c| 995 +
include/fpu/softfloat.h| 9 +-
target-mips/msa_helper.c | 56 +--
4 files changed, 617 inser
Expand out and remove the STATUS macro.
Signed-off-by: Peter Maydell
---
fpu/softfloat-specialize.h | 24 ++---
fpu/softfloat.c| 239 ++---
include/fpu/softfloat.h| 30 +++---
3 files changed, 167 insertions(+), 126 deletions(-)
diff --g
The following patch file (a cut down lump of an actual change
I was making) seems to cause scripts/checkpatch.pl to hang.
I find that script too opaque to try to debug, but I post the
offending input here in case anybody else wishes to investigate.
begin
commit 4b3cf48c7fa455eb3b31dc844c95
On Wed, 2015-01-28 at 16:37 +0800, Chen Fan wrote:
> for old machine types, we should disable aercap feature.
>
> Signed-off-by: Chen Fan
> ---
> hw/vfio/pci.c | 13 ++---
> include/hw/compat.h | 4
> 2 files changed, 14 insertions(+), 3 deletions(-)
>
> diff --git a/hw/vfio
On Wed, 2015-01-28 at 16:37 +0800, Chen Fan wrote:
> when the vfio device encounters an uncorrectable error in host,
> the vfio_pci driver will signal the eventfd registered by this
> vfio device, the results in the qemu eventfd handler getting
> invoked.
>
> this patch is to pass the error to gue
On Wed, 2015-01-28 at 16:37 +0800, Chen Fan wrote:
> if we detect the aer capability in vfio device, then
> we should initialize the vfio device aer rigister bits.
> so guest OS can set this bits as needed.
s/rigister/register/
> Signed-off-by: Chen Fan
> ---
> hw/vfio/pci.c | 72
> +++
On Wed, 2015-01-28 at 16:37 +0800, Chen Fan wrote:
The "why" should go here
> Signed-off-by: Chen Fan
> ---
> hw/vfio/pci.c | 8 ++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/hw/vfio/pci.c b/hw/vfio/pci.c
> index 54eb6b4..65247ee 100644
> --- a/hw/vfio/pci.c
> ++
On Fri, Jan 30, 2015 at 08:37:47AM +0100, Jan Kiszka wrote:
> On 2015-01-30 00:06, Paolo Bonzini wrote:
> >
> >
> > On 29/01/2015 20:37, Marc Marí wrote:
> >> Is this an expected behaviour? I can't see why.
> >>
> >> I'd like to know if there is a certain reason why it doesn't work. Or
> >> if it
On 02/02/15 22:58, Peter Lieven wrote:
Am 02.02.2015 um 19:29 schrieb Denis V. Lunev:
qemu_gluster_co_discard calculates size to discard as follows
size_t size = nb_sectors * BDRV_SECTOR_SIZE;
ret = glfs_discard_async(s->fd, offset, size, &gluster_finish_aiocb, acb);
glfs_discard_asyn
Changes from v2:
- dropped conditional in patch gluster code
Changes from v1:
- switched to UINT32_MAX for NBD
- limited max_discard for gluster to SIZE_MAX on i686 only
Signed-off-by: Denis V. Lunev
CC: Kevin Wolf
CC: Peter Lieven
qemu_gluster_co_discard calculates size to discard as follows
size_t size = nb_sectors * BDRV_SECTOR_SIZE;
ret = glfs_discard_async(s->fd, offset, size, &gluster_finish_aiocb, acb);
glfs_discard_async is declared as follows:
int glfs_discard_async (glfs_fd_t *fd, off_t length, size_t len
nbd_co_discard calls nbd_client_session_co_discard which uses uint32_t
as the length in bytes of the data to discard due to the following
definition:
struct nbd_request {
uint32_t magic;
uint32_t type;
uint64_t handle;
uint64_t from;
uint32_t len; <-- the length of data to be d
Am 02.02.2015 um 19:29 schrieb Denis V. Lunev:
> qemu_gluster_co_discard calculates size to discard as follows
> size_t size = nb_sectors * BDRV_SECTOR_SIZE;
> ret = glfs_discard_async(s->fd, offset, size, &gluster_finish_aiocb, acb);
>
> glfs_discard_async is declared as follows:
> int g
Am 02.02.2015 um 19:29 schrieb Denis V. Lunev:
> nbd_co_discard calls nbd_client_session_co_discard which uses uint32_t
> as the length in bytes of the data to discard due to the following
> definition:
>
> struct nbd_request {
> uint32_t magic;
> uint32_t type;
> uint64_t handle;
>
On 2015-02-02 at 14:46, Kevin Wolf wrote:
Am 26.01.2015 um 16:00 hat Max Reitz geschrieben:
Now that request clamping is done in the BlockBackend, the "growable"
field can be removed from the BlockDriverState. All BDSs are now treated
as being "growable" (that is, they are allowed to grow; they
From: "Dr. David Alan Gilbert"
Turn all the D/DD/DDDPRINTFs into trace events
Turn most of the fprintf(stderr, into error_report
Signed-off-by: Dr. David Alan Gilbert
---
migration/rdma.c | 333 ---
trace-events | 62 +++
2 files
On 2015-02-02 at 14:36, Kevin Wolf wrote:
Am 27.01.2015 um 18:11 hat Max Reitz geschrieben:
On 2015-01-27 at 12:10, Eric Blake wrote:
On 01/27/2015 10:04 AM, Max Reitz wrote:
On 2015-01-27 at 11:59, Eric Blake wrote:
On 01/26/2015 08:00 AM, Max Reitz wrote:
Remove "growable" option from the
On 2015-02-02 at 14:34, Kevin Wolf wrote:
Am 26.01.2015 um 16:00 hat Max Reitz geschrieben:
Signed-off-by: Max Reitz
---
qemu-io.c | 31 ---
1 file changed, 12 insertions(+), 19 deletions(-)
diff --git a/qemu-io.c b/qemu-io.c
index 91a445a..81f8f64 100644
--- a/q
Am 26.01.2015 um 16:00 hat Max Reitz geschrieben:
> This series removes the "growable" field from the BlockDriverState
> object. Its use was to clamp guest requests against the limits of the
> BDS; however, this can now be done more easily by moving those checks
> into the BlockBackend functions.
>
On 2015-02-02 at 14:00, Kevin Wolf wrote:
Am 26.01.2015 um 16:00 hat Max Reitz geschrieben:
Signed-off-by: Max Reitz
---
qemu-img.c | 57 -
1 file changed, 24 insertions(+), 33 deletions(-)
diff --git a/qemu-img.c b/qemu-img.c
index be
Am 26.01.2015 um 16:00 hat Max Reitz geschrieben:
> Now that request clamping is done in the BlockBackend, the "growable"
> field can be removed from the BlockDriverState. All BDSs are now treated
> as being "growable" (that is, they are allowed to grow; they are not
> necessarily actually able to)
On 2015-02-02 at 13:35, Kevin Wolf wrote:
Am 26.01.2015 um 16:00 hat Max Reitz geschrieben:
Signed-off-by: Max Reitz
---
qemu-img.c | 20 ++--
1 file changed, 6 insertions(+), 14 deletions(-)
diff --git a/qemu-img.c b/qemu-img.c
index 4e9a7f5..be1953d 100644
--- a/qemu-img.c
On 2015-02-02 at 13:27, Kevin Wolf wrote:
Am 26.01.2015 um 16:00 hat Max Reitz geschrieben:
Signed-off-by: Max Reitz
---
hw/block/xen_disk.c | 28
1 file changed, 12 insertions(+), 16 deletions(-)
diff --git a/hw/block/xen_disk.c b/hw/block/xen_disk.c
index 2184
Am 27.01.2015 um 18:11 hat Max Reitz geschrieben:
> On 2015-01-27 at 12:10, Eric Blake wrote:
> >On 01/27/2015 10:04 AM, Max Reitz wrote:
> >>On 2015-01-27 at 11:59, Eric Blake wrote:
> >>>On 01/26/2015 08:00 AM, Max Reitz wrote:
> Remove "growable" option from the "open" command and from the q
On 13/01/2015 09:53, Fam Zheng wrote:
> We have module build support around for a while, but also had it bitrot
> several times. It probably makes sense to enable it by default so that
> people can notice and use it.
>
> Counterpart to --enable-modules, which is turned as default,
> --disable-mo
Am 26.01.2015 um 16:00 hat Max Reitz geschrieben:
> Signed-off-by: Max Reitz
> ---
> qemu-io.c | 31 ---
> 1 file changed, 12 insertions(+), 19 deletions(-)
>
> diff --git a/qemu-io.c b/qemu-io.c
> index 91a445a..81f8f64 100644
> --- a/qemu-io.c
> +++ b/qemu-io.c
> @@
The following changes since commit 83761b9244ad2ed39d3cfabe8a0e901ab906f7bf:
Merge remote-tracking branch 'remotes/riku/tags/pull-linux-user-20150127'
into staging (2015-01-27 22:25:56 +)
are available in the git repository at:
git://github.com/bonzini/qemu.git tags/for-upstream
for y
Am 26.01.2015 um 16:00 hat Max Reitz geschrieben:
> Signed-off-by: Max Reitz
> ---
> qemu-img.c | 57 -
> 1 file changed, 24 insertions(+), 33 deletions(-)
>
> diff --git a/qemu-img.c b/qemu-img.c
> index be1953d..0b23c87 100644
> --- a/qem
Am 26.01.2015 um 16:00 hat Max Reitz geschrieben:
> Signed-off-by: Max Reitz
> ---
> qemu-img.c | 20 ++--
> 1 file changed, 6 insertions(+), 14 deletions(-)
>
> diff --git a/qemu-img.c b/qemu-img.c
> index 4e9a7f5..be1953d 100644
> --- a/qemu-img.c
> +++ b/qemu-img.c
> @@ -291,3
Changes from v1:
- switched to UINT32_MAX for NBD
- limited max_discard for gluster to SIZE_MAX on i686 only
Signed-off-by: Denis V. Lunev
CC: Kevin Wolf
CC: Peter Lieven
nbd_co_discard calls nbd_client_session_co_discard which uses uint32_t
as the length in bytes of the data to discard due to the following
definition:
struct nbd_request {
uint32_t magic;
uint32_t type;
uint64_t handle;
uint64_t from;
uint32_t len; <-- the length of data to be d
qemu_gluster_co_discard calculates size to discard as follows
size_t size = nb_sectors * BDRV_SECTOR_SIZE;
ret = glfs_discard_async(s->fd, offset, size, &gluster_finish_aiocb, acb);
glfs_discard_async is declared as follows:
int glfs_discard_async (glfs_fd_t *fd, off_t length, size_t len
Am 26.01.2015 um 16:00 hat Max Reitz geschrieben:
> Signed-off-by: Max Reitz
> ---
> hw/block/xen_disk.c | 28
> 1 file changed, 12 insertions(+), 16 deletions(-)
>
> diff --git a/hw/block/xen_disk.c b/hw/block/xen_disk.c
> index 21842a0..1b0257c 100644
> --- a/hw/bl
On 2 February 2015 at 18:16, Paolo Bonzini wrote:
> Can you merge up to commit 2aeba9d8a1b6121b98948fcd42fd2aa32f68b750 only
> or should I respin without the final patch?
My pullreq-application script doesn't like merging things which
aren't branches or tags, I'm afraid. Can you respin?
-- PMM
On 02/02/2015 18:54, Peter Maydell wrote:
> On 2 February 2015 at 16:29, Paolo Bonzini wrote:
>> The important bits here are the first part of RCU and enabling
>> modules by default. They have been tested with Travis for a few
>> days now, and things seem okay.
>>
>> v1->v2 changes are the new
On 01/26/2015 07:53 AM, Leon Alrae wrote:
> The test is supposed to terminate TB if the end of the page is reached.
> However, with current implementation it may never succeed for microMIPS or
> mips16.
>
> Reported-by: Richard Henderson
> Signed-off-by: Leon Alrae
> ---
> target-mips/translate
On 2 February 2015 at 16:29, Paolo Bonzini wrote:
> The important bits here are the first part of RCU and enabling
> modules by default. They have been tested with Travis for a few
> days now, and things seem okay.
>
> v1->v2 changes are the new qemu-thread patch to fix Mac OS X,
> and cleaning u
On 2015-01-29 at 04:36, Markus Armbruster wrote:
v2:
* PATCH 4: Use error_setg() [Kevin]
* R-bys retained
Markus Armbruster (4):
blockdev: Give find_block_job() an Error ** parameter
blockdev: Eliminate silly QERR_BLOCK_JOB_NOT_ACTIVE macro
block: New bdrv_add_key(), convert monitor to
On 02/02/15 20:34, Paolo Bonzini wrote:
On 02/02/2015 18:00, Denis V. Lunev wrote:
You are absolutely correct for NBD case but I do not get the
point about SIZE_MAX for gluster. There is no such definition
in their git at git://github.com/gluster/glusterfs nor in
public API headers in Ubuntu
On 02/02/2015 18:00, Denis V. Lunev wrote:
>>
> You are absolutely correct for NBD case but I do not get the
> point about SIZE_MAX for gluster. There is no such definition
> in their git at git://github.com/gluster/glusterfs nor in
> public API headers in Ubuntu :(
SIZE_MAX is defined in stdint
This adds tests for overriding the qemu-internal BDRV_O_PROTOCOL flag by
explicitly specifying a block driver. As one test must be run over the
NBD protocol while the other must not, this patch adds two separate
iotests.
Signed-off-by: Max Reitz
---
tests/qemu-iotests/119 | 60 ++
The BDRV_O_PROTOCOL flag should have an impact only if no driver is
specified explicitly. Therefore, if bdrv_open() is called with an
explicit block driver argument (either through the options QDict or
through the drv parameter) and that block driver is a protocol block
driver, BDRV_O_PROTOCOL shou
BDRV_O_PROTOCOL is an internal qemu flag which a user should be able to
override by explicitly specifying a block driver. This series implements
this and adds two iotests (one for NBD, one for file) to test it.
For the NBD test to succeed, this series relies on
"iotests: Specify format for qemu-nb
On 02/02/15 19:45, Kevin Wolf wrote:
Am 02.02.2015 um 17:25 hat Denis V. Lunev geschrieben:
On 02/02/15 19:13, Kevin Wolf wrote:
Am 02.02.2015 um 15:48 hat Peter Lieven geschrieben:
do not trim requests if the driver does not supply a limit
through BlockLimits. For write zeroes we still keep a
Am 02.02.2015 um 17:25 hat Denis V. Lunev geschrieben:
> On 02/02/15 19:13, Kevin Wolf wrote:
> >Am 02.02.2015 um 15:48 hat Peter Lieven geschrieben:
> >>do not trim requests if the driver does not supply a limit
> >>through BlockLimits. For write zeroes we still keep a limit
> >>for the unsupporte
The following sequence
int fd = open(argv[1], O_RDWR | O_CREAT | O_DIRECT, 0644);
for (i = 0; i < 10; i++)
write(fd, buf, 4096);
performs 5% better if buf is aligned to 4096 bytes.
The difference is quite reliable.
On the other hand we do not want at the moment to enforce
Hi,
On Mon, Feb 02, 2015 at 07:27:10AM +, David Woodhouse wrote:
> On Sun, 2015-02-01 at 21:07 -0800, David Miller wrote:
> > From: David Woodhouse
> > Date: Sun, 01 Feb 2015 21:29:43 +
> >
> > > I really was looking for some way to push down something like an XFRM
> > > state into the t
On 02/02/15 19:47, Paolo Bonzini wrote:
On 02/02/2015 17:44, Denis V. Lunev wrote:
+++ b/block/raw-posix.c
@@ -667,7 +667,8 @@ static void raw_refresh_limits(BlockDriverState *bs, Error
**errp)
BDRVRawState *s = bs->opaque;
raw_probe_alignment(bs, s->fd, errp);
-bs->bl.opt_
On 02/02/2015 17:44, Denis V. Lunev wrote:
> +++ b/block/raw-posix.c
> @@ -667,7 +667,8 @@ static void raw_refresh_limits(BlockDriverState *bs,
> Error **errp)
> BDRVRawState *s = bs->opaque;
>
> raw_probe_alignment(bs, s->fd, errp);
> -bs->bl.opt_mem_alignment = s->buf_align;
>
The following sequence
int fd = open(argv[1], O_RDWR | O_CREAT | O_DIRECT, 0644);
for (i = 0; i < 10; i++)
write(fd, buf, 4096);
iperforms 5% better if buf is aligned to 4096 bytes rather then to
512 bytes.
I have used the following program to test
#define _GNU_SOURCE
#inc
qemu_gluster_co_discard calculates size to discard as follows
size_t size = nb_sectors * BDRV_SECTOR_SIZE;
ret = glfs_discard_async(s->fd, offset, size, &gluster_finish_aiocb, acb);
glfs_discard_async is declared as follows:
int glfs_discard_async (glfs_fd_t *fd, off_t length, size_t len
nbd_co_discard calls nbd_client_session_co_discard which uses uint32_t
as the length in bytes of the data to discard due to the following
definition:
struct nbd_request {
uint32_t magic;
uint32_t type;
uint64_t handle;
uint64_t from;
uint32_t len; <-- the length of data to be d
On 02/02/2015 16:03, Peter Maydell wrote:
> On 2 February 2015 at 14:55, Paolo Bonzini wrote:
>> and if it still fails, catch a backtrace of all threads?
Whoa, this has been broken for a long, long time.
Paolo
> (gdb) thread apply all backtrace
>
> Thread 9 (process 42110):
> #0 0x7fff9
The following changes since commit 83761b9244ad2ed39d3cfabe8a0e901ab906f7bf:
Merge remote-tracking branch 'remotes/riku/tags/pull-linux-user-20150127'
into staging (2015-01-27 22:25:56 +)
are available in the git repository at:
git://github.com/bonzini/qemu.git tags/for-upstream
for y
On 02/02/15 19:13, Kevin Wolf wrote:
Am 02.02.2015 um 15:48 hat Peter Lieven geschrieben:
do not trim requests if the driver does not supply a limit
through BlockLimits. For write zeroes we still keep a limit
for the unsupported path to avoid allocating a big bounce buffer.
Suggested-by: Kevin
Am 02.02.2015 um 15:48 hat Peter Lieven geschrieben:
> do not trim requests if the driver does not supply a limit
> through BlockLimits. For write zeroes we still keep a limit
> for the unsupported path to avoid allocating a big bounce buffer.
>
> Suggested-by: Kevin Wolf
> Suggested-by: Denis V.
Am 02.02.2015 um 14:52 hat Peter Lieven geschrieben:
> some remarks:
> - i introduced rd_merged and wr_merged block accounting stats to
>blockstats as a generic interface which can be set from any
>driver that will introduce multirequest merging in the future.
> - the old multiwrite inter
On Fri, 23 Jan 2015 15:42:30 +0200
"Michael S. Tsirkin" wrote:
> On Fri, Jan 23, 2015 at 02:32:45PM +0100, Igor Mammedov wrote:
> > On Fri, 23 Jan 2015 10:59:48 +0200
> > "Michael S. Tsirkin" wrote:
> >
> > > On Thu, Jan 22, 2015 at 02:49:50PM +, Igor Mammedov wrote:
> > > > Signed-off-by:
This had a possible deadlock that was visible with rcutorture.
qemu_event_setqemu_event_wait
cmpxchg reads FREE, writes BUSY
fute
On Mon, 2015-02-02 at 16:23 +0100, Phil Sutter wrote:
> Since you want to provide connectivity over HTTPS which is not possible
> in kernel space, you are stuck with keeping the tun device. So the
> packet flow in that case is identical to how e.g. OpenVPN does it:
>
> - tunX holds default route
>
Ping
On Mon, Jan 12, 2015 at 03:58:14PM +, Daniel P. Berrange wrote:
> Add a new 'guest-set-admin-password' command for changing the
> root/administrator password. This command is needed to allow
> OpenStack to support its API for changing the admin password
> on a running guest.
>
> Accepts
On 02/02/15 17:49, Kevin Wolf wrote:
Am 02.02.2015 um 15:20 hat Peter Lieven geschrieben:
Am 02.02.2015 um 15:16 schrieb Kevin Wolf:
Am 02.02.2015 um 15:12 hat Peter Lieven geschrieben:
Am 02.02.2015 um 15:04 schrieb Kevin Wolf:
Am 02.02.2015 um 14:55 hat Peter Lieven geschrieben:
Am 02.02.2
On Mon, 2015-02-02 at 09:24 +0100, Steffen Klassert wrote:
>
> Maybe you want to use a virtual tunnel interface (vti) what we have
> already. Everything that is routed through such an interface is
> guaranteed to be either encrypted if a matching xfrm state is present
> or dropped. Same on the rce
in case we send and update for a complete scanline increment
the y offset to avoid running to find_next_bit for that lines
twice.
Signed-off-by: Peter Lieven
---
ui/vnc.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/ui/vnc.c b/ui/vnc.c
index a742c90..6fa2ee7 100644
--- a/ui/vnc.c
++
1 - 100 of 188 matches
Mail list logo
