Hi, Ashok
Please add " original author by Huang Ying " at some
place.
Thanks.
> -Original Message-
> From: Raj, Ashok
> Sent: Friday, December 11, 2015 3:41 AM
> To: k...@vger.kernel.org
> Cc: Chen, Gong; Gleb Natapov; Paolo Bonzini; qemu-devel@nongnu.org;
> linux-ker...@vger.kernel.org;
David,
Thanks for including my email directly. It helps a lot.
Below, I'm going to assume that only "dest" is calling
qemu_rdma_exchange_recv()
and only src is calling qemu_rdma_exchange_send(), since you didn't specify
who
is sending and who is receiving.
If that assumption is wrong, please res
Mac OS X can be picky when it comes to allowing the user
to use physical devices in QEMU. Most mounted volumes
appear to be off limits to QEMU. If an issue is detected,
a message is displayed showing the user how to unmount a
volume. Now QEMU uses both CD and DVD media.
Signed-off-by: John Arbuckl
On 12/12/15 08:41, Richard Henderson wrote:
> On 12/11/2015 03:38 PM, Chen Gang wrote:
>>
>> On 12/11/15 05:17, Richard Henderson wrote:
>>> On 12/10/2015 06:15 AM, Chen Gang wrote:
+#define TILEGX_F_MAN_HBIT (1ULL << 59)
>>> ...
+static uint64_t fr_to_man(float64 d)
+{
+
For more complex BDS trees that can be created under normal circumstances,
we lose the ability to issue query commands because of our inability to
re-construct the absolute filename.
Instead, omit this field when it is a problem and present as much information
as we can.
This will change the expe
Max: Did you have in mind something like this?
v2:
- Fix qemu-img from now choking when it gets a partial response.
For convenience, this branch is available at:
https://github.com/jnsnow/qemu.git branch block-allo
...But only if we have the backing_filename. It means something Scary
happened and we can't really be quite exactly sure if we can trust the
backing_filename.
Signed-off-by: John Snow
---
qemu-img.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/qemu-img.c b/qemu-img.c
i
If it happens to match the backing path, that was the actual path.
Signed-off-by: John Snow
---
block/qapi.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/block/qapi.c b/block/qapi.c
index 267f147..01569da 100644
--- a/block/qapi.c
+++ b/block/qapi.c
@@ -676,7 +676,9 @@
Always report full_backing_filename, even if it's the same as
backing_filename. In the next patch, full_backing_filename may be
omitted if it cannot be generated instead of allowing e.g. drive_query
to abort if it runs into this scenario.
The presence or absence of the "full" field becomes useful
On 12/10/2015 10:27 PM, Eric Blake wrote:
> On my machine, './check -qcow2 028' was failing about 80% of the
> time, due to a race in how many times the repeated attempts
> to run 'info block-jobs' could occur before the job was done,
> showing up as a failure of fewer '(qemu) ' prompts than in t
On 12/11/2015 03:38 PM, Chen Gang wrote:
On 12/11/15 05:17, Richard Henderson wrote:
On 12/10/2015 06:15 AM, Chen Gang wrote:
+#define TILEGX_F_MAN_HBIT (1ULL << 59)
...
+static uint64_t fr_to_man(float64 d)
+{
+uint64_t val = get_f64_man(d) << 7;
+
+if (get_f64_exp(d)) {
+
On 12/11/2015 04:40 PM, Programmingkid wrote:
> I guess the commit message is a little out of date. How about this:
>
> Mac OS X can be picky when it comes to allowing the user
> to use physical devices in QEMU. Most mounted volumes
> appear to be off limits to QEMU. If an issue is detected,
> a
Hello,
On behalf of the QEMU Team, I'd like to announce the availability of the
fourth release candidate for the QEMU 2.5 release. This release is meant
for testing purposes and should not be used in a production environment.
http://wiki.qemu.org/download/qemu-2.5.0-rc4.tar.bz2
You can help i
On Dec 11, 2015, at 5:00 PM, Jeff Cody wrote:
> On Thu, Dec 10, 2015 at 09:39:51AM -0500, Programmingkid wrote:
>> https://patchwork.ozlabs.org/patch/550295/
>>
>> Mac OS X can be picky when it comes to allowing the user
>> to use physical devices in QEMU. Most mounted volumes
>> appear to be of
On 12/10/2015 10:47 AM, Sergey Fedorov wrote:
The "PC advancement" trick was used just after recognizing that a
breakpoint exception was going to be generated. This trick has had two
points:
1. Guarantee that tb->size isn't zero: there are many places where it's
expected to be non-zero. In
On 12/11/15 05:17, Richard Henderson wrote:
> On 12/10/2015 06:15 AM, Chen Gang wrote:
>> +#define TILEGX_F_MAN_HBIT (1ULL << 59)
> ...
>> +static uint64_t fr_to_man(float64 d)
>> +{
>> +uint64_t val = get_f64_man(d) << 7;
>> +
>> +if (get_f64_exp(d)) {
>> +val |= TILEGX_F_MAN_HB
Hello,
Thomas, this is the last refactoring patch which doesn't have a review
yet, right?
Samuel
Samuel Thibault, on Fri 11 Dec 2015 01:15:17 +0100, wrote:
> From: Guillaume Subiron
>
> This patch factorizes some duplicate code into a new function,
> sotranslate_out(). This function perform th
On 11 December 2015 at 19:01, Kevin O'Connor wrote:
> On Fri, Dec 11, 2015 at 04:37:06PM +, Peter Maydell wrote:
>> Update the SDHCI code to use the new SDBus APIs.
>>
>> This commit introduces the new command line options required
>> to connect a disk to sdhci-pci:
>>
>> -device sdhci-pci -d
On Thu, Dec 10, 2015 at 09:39:51AM -0500, Programmingkid wrote:
> https://patchwork.ozlabs.org/patch/550295/
>
> Mac OS X can be picky when it comes to allowing the user
> to use physical devices in QEMU. Most mounted volumes
> appear to be off limits to QEMU. If an issue is detected,
> a message
Thomas Huth, on Fri 11 Dec 2015 14:38:44 +0100, wrote:
> Also, I'd prefer if you could split this patch into two: One for
> renaming the "arp_requested" field, and one for adding the additional
> logic with the switch statement (since there are two different kind of
> changes).
Ok, at least it's e
Samuel Thibault, on Fri 11 Dec 2015 20:51:02 +0100, wrote:
> Samuel Thibault, on Fri 11 Dec 2015 20:38:19 +0100, wrote:
> > I'll however have a look at introducing the optimizations etc. first, so
> > that both making solookup use sockaddr and introducing sockaddr_equal
> > looks natural.
>
> Yes,
Samuel Thibault, on Fri 11 Dec 2015 20:38:19 +0100, wrote:
> I'll however have a look at introducing the optimizations etc. first, so
> that both making solookup use sockaddr and introducing sockaddr_equal
> looks natural.
Yes, it seems to be working very nicely.
Samuel
Samuel Thibault, on Fri 11 Dec 2015 20:29:44 +0100, wrote:
> Thomas Huth, on Fri 11 Dec 2015 16:06:22 +0100, wrote:
> > On 11/12/15 01:15, Samuel Thibault wrote:
> > > From: Guillaume Subiron
> > >
> > > This patch makes solookup() compatible with varying address families.
> > > Also,
> > > this
Thomas Huth, on Fri 11 Dec 2015 16:06:22 +0100, wrote:
> On 11/12/15 01:15, Samuel Thibault wrote:
> > From: Guillaume Subiron
> >
> > This patch makes solookup() compatible with varying address families. Also,
> > this function was only compatible with TCP. Having the socket list in
> > argument
This moves all data from PcGuestInfo to either PCMachineState or
PCMachineClass.
This series depends on other two series:
* [PATCH v3 0/6] pc: Initialization and compat function cleanup
* [PATCH V3 0/3] hw/pcie: Multi-root support for Q35
For reference, there's a git tree containing this series p
On Fri, Dec 11, 2015 at 04:37:06PM +, Peter Maydell wrote:
> Update the SDHCI code to use the new SDBus APIs.
>
> This commit introduces the new command line options required
> to connect a disk to sdhci-pci:
>
> -device sdhci-pci -drive id=mydrive,[...] -device sd,drive=mydrive
I can't rev
Signed-off-by: Eduardo Habkost
---
hw/i386/acpi-build.c | 7 +++
hw/i386/pc.c | 10 --
include/hw/i386/pc.h | 2 +-
3 files changed, 8 insertions(+), 11 deletions(-)
diff --git a/hw/i386/acpi-build.c b/hw/i386/acpi-build.c
index 9598eac..43d8166 100644
--- a/hw/i386/acpi-bu
The code can use the PCMachineClass.pci_enabled field directly.
Signed-off-by: Eduardo Habkost
---
hw/i386/pc.c | 2 +-
hw/i386/pc_piix.c| 5 +
hw/i386/pc_q35.c | 4 +---
include/hw/i386/pc.h | 1 -
4 files changed, 3 insertions(+), 9 deletions(-)
diff --git a/hw/i386/pc.c b
We don't need to save the pointer on AcpiBuildState, as it is not
used anymore.
Signed-off-by: Eduardo Habkost
---
hw/i386/acpi-build.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/hw/i386/acpi-build.c b/hw/i386/acpi-build.c
index 92d25c9..82d55bb 100644
--- a/hw/i386/acpi-build.c
+++ b
Remove the fields: legacy_acpi_table_size, has_acpi_build,
has_reserved_memory, and rsdp_in_ram from PcGuestInfo, and let
the existing code use the PCMachineClass fields directly.
Signed-off-by: Eduardo Habkost
---
hw/i386/acpi-build.c | 10 ++
hw/i386/pc.c | 6 +++---
hw/i386/p
We can use PC_MACHINE(qdev_get_machine())->acpi_guest_info to get
guest_info.
Signed-off-by: Eduardo Habkost
---
hw/i386/acpi-build.c | 35 +--
hw/i386/acpi-build.h | 2 +-
hw/i386/pc.c | 2 +-
3 files changed, 23 insertions(+), 16 deletions(-)
diff --g
The struct is not used for anything, now.
Signed-off-by: Eduardo Habkost
---
hw/i386/pc.c | 4 +---
include/hw/i386/pc.h | 7 +--
2 files changed, 2 insertions(+), 9 deletions(-)
diff --git a/hw/i386/pc.c b/hw/i386/pc.c
index 43a25a0..f78b877 100644
--- a/hw/i386/pc.c
+++ b/hw/i386/
The ACPI code can use the PCMachineState fields directly.
Signed-off-by: Eduardo Habkost
---
hw/i386/acpi-build.c | 10 +-
hw/i386/pc.c | 2 --
include/hw/i386/pc.h | 1 -
3 files changed, 5 insertions(+), 8 deletions(-)
diff --git a/hw/i386/acpi-build.c b/hw/i386/acpi-build.c
We can get the PcGuestInfo struct directly from PCMachineState,
and the return value is not needed at all.
Signed-off-by: Eduardo Habkost
---
hw/i386/pc.c | 5 ++---
hw/i386/pc_piix.c| 2 +-
include/hw/i386/pc.h | 3 +--
3 files changed, 4 insertions(+), 6 deletions(-)
diff --git a/
We can get the PcGuestInfo struct directly from PCMachineState,
and the return value is not needed at all.
Signed-off-by: Eduardo Habkost
---
hw/i386/pc.c | 11 +--
hw/i386/pc_piix.c| 2 +-
hw/i386/pc_q35.c | 2 +-
include/hw/i386/pc.h | 9 -
4 files changed, 1
Signed-off-by: Eduardo Habkost
---
hw/i386/acpi-build.c | 22 +-
hw/i386/pc.c | 20 ++--
include/hw/i386/pc.h | 14 +-
3 files changed, 28 insertions(+), 28 deletions(-)
diff --git a/hw/i386/acpi-build.c b/hw/i386/acpi-build.c
index 43d8166
Group related PCMachineState and PCMachineClass fields into
sections, and move existing field descriptions to doc comments.
Signed-off-by: Eduardo Habkost
---
include/hw/i386/pc.h | 48
1 file changed, 36 insertions(+), 12 deletions(-)
diff --git
Instead of allocating a new struct just for PcGuestInfo and the
mchine_done Notifier, place them inside PCMachineState.
Signed-off-by: Eduardo Habkost
---
hw/i386/pc.c | 27 ++-
include/hw/i386/pc.h | 2 ++
2 files changed, 12 insertions(+), 17 deletions(-)
diff
The struct will be used inside PCMachineState.
Signed-off-by: Eduardo Habkost
---
include/hw/i386/pc.h | 31 ---
1 file changed, 16 insertions(+), 15 deletions(-)
diff --git a/include/hw/i386/pc.h b/include/hw/i386/pc.h
index 9503dbb..84bc88f 100644
--- a/include/hw/
The field is not used for anything.
Signed-off-by: Eduardo Habkost
---
hw/i386/pc_q35.c | 1 -
include/hw/pci-host/q35.h | 1 -
2 files changed, 2 deletions(-)
diff --git a/hw/i386/pc_q35.c b/hw/i386/pc_q35.c
index 9da751b..43ee8bb 100644
--- a/hw/i386/pc_q35.c
+++ b/hw/i386/pc_q35.c
@
We don't want newlines embedded in error messages. This seems to be a common
problem with new code so let's try to catch it with checkpatch.
This will not catch cases where newlines are inserted into the middle of an
existing multi-line statement. But those cases should be rare.
Signed-off-by: Ja
On 12/11/2015 09:52 AM, Jason J. Herne wrote:
We don't want newlines embedded in error messages. This seems to be a common
problem with new code so let's try to catch it with checkpatch.
This does not catch the newline when it is in a multiline statement. This is
quite a bit more difficult and c
On 12/11/15 17:17, Eric Blake wrote:
> On 12/11/2015 08:40 AM, Laszlo Ersek wrote:
>> meta
>>
>> On 12/11/15 16:09, Thomas Huth wrote:
>>> On 11/12/15 15:55, Samuel Thibault wrote:
Thomas Huth, on Fri 11 Dec 2015 15:32:48 +0100, wrote:
> So maybe it's better to do smaller steps instead: Wo
Hi Michael,
I think I've got an RDMA race condition, but I'm being a little
cautious at the moment and wondered if you agree with the following
diagnosis.
It's showing up in a world of mine that's sending more control messages
from the destination->source and I'm seeing the following.
We norma
Three in comments and one in code in the stub tcg_liveness_analysis.
Signed-off-by: Richard Henderson
---
target-arm/translate.c | 3 +--
target-i386/translate.c | 3 +--
target-unicore32/translate.c | 3 +--
tcg/tcg.c| 3 +--
4 files changed, 4 insertions(+), 8 de
On 12/11/2015 05:41 AM, Peter Maydell wrote:
Hi; I noticed while grepping through code that the version of
tcg_liveness_analysis() in tcg/tcg.c for #ifndef USE_LIVENESS_ANALYSIS
won't compile because it's still referring to the no-longer-existent
TCGContext::gen_opc_buf.
Oops.
Richard, I thin
On 11 December 2015 at 17:01, Stefano Stabellini
wrote:
> On Fri, 11 Dec 2015, Peter Maydell wrote:
>> On 11 December 2015 at 16:52, Stefano Stabellini
>> wrote:
>> If this was intended for 2.5 you have missed the boat.
>
> I sent it because it is a bug fix, but waiting for 2.6 also makes
> sense
On Fri, 11 Dec 2015, Peter Maydell wrote:
> On 11 December 2015 at 16:52, Stefano Stabellini
> wrote:
> > The following changes since commit 6e0abc251dd4f8eba1f53656dfede12e5840e83b:
> >
> > blockdev: Mark {insert, remove}-medium experimental (2015-12-11 15:39:29
> > +)
> >
> > are availabl
On Fri, 2015-12-11 at 16:44 +, Stefano Stabellini wrote:
>
> It is not possible to do this at runtime. I think we should do this at
> compile time because in any case it is not supported to run a QEMU built
> for a given Xen version on a different Xen version.
I am currently working pretty h
On 11 December 2015 at 16:52, Stefano Stabellini
wrote:
> The following changes since commit 6e0abc251dd4f8eba1f53656dfede12e5840e83b:
>
> blockdev: Mark {insert, remove}-medium experimental (2015-12-11 15:39:29
> +)
>
> are available in the git repository at:
>
> git://xenbits.xen.org/pe
The following changes since commit 6e0abc251dd4f8eba1f53656dfede12e5840e83b:
blockdev: Mark {insert, remove}-medium experimental (2015-12-11 15:39:29
+)
are available in the git repository at:
git://xenbits.xen.org/people/sstabellini/qemu-dm.git tags/xen-2015-12-11
for you to fetch cha
The Xen toolstack uses "vhd" to specify a disk in VHD format, however
the name of the driver in QEMU is "vpc". Replace "vhd" with "vpc", so
that QEMU can find the right driver to use for it.
Signed-off-by: Stefano Stabellini
---
hw/block/xen_disk.c |3 +++
1 file changed, 3 insertions(+)
di
Update the SDHCI code to use the new SDBus APIs.
This commit introduces the new command line options required
to connect a disk to sdhci-pci:
-device sdhci-pci -drive id=mydrive,[...] -device sd,drive=mydrive
Signed-off-by: Peter Maydell
---
hw/sd/sdhci.c | 95
Convert the pxa2xx_mmci device from manual save/load
functions to a VMStateDescription structure.
This is a migration compatibility break.
Signed-off-by: Peter Maydell
---
hw/sd/pxa2xx_mmci.c | 148
1 file changed, 56 insertions(+), 92 deleti
Convert the pxa2xx_mmci device to be a sysbus device.
In this commit we only change the device itself, and leave
the interface to the SD card using the old non-SDBus APIs.
Signed-off-by: Peter Maydell
---
hw/sd/pxa2xx_mmci.c | 73 -
1 file cha
Convert the sd_reset() function into a proper Device reset method.
Signed-off-by: Peter Maydell
---
hw/sd/sd.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/hw/sd/sd.c b/hw/sd/sd.c
index 7c79217..b4a5a62 100644
--- a/hw/sd/sd.c
+++ b/hw/sd/sd.c
@@ -393,8 +393,9 @
Now the PXA2xx MMCI device is QOMified itself, we can
update it to use the SDBus APIs to talk to the SD card.
Signed-off-by: Peter Maydell
---
hw/sd/pxa2xx_mmci.c | 80 +++--
1 file changed, 66 insertions(+), 14 deletions(-)
diff --git a/hw/sd/pxa
Add a reset function to the pxa2xx_mmci device; previously it had
no handling for system reset at all.
Signed-off-by: Peter Maydell
---
hw/sd/pxa2xx_mmci.c | 37 +
1 file changed, 37 insertions(+)
diff --git a/hw/sd/pxa2xx_mmci.c b/hw/sd/pxa2xx_mmci.c
index 8
Move the creation of the SD card device from the sdhci_sysbus
device itself into the boards that create these devices.
This allows us to remove the cannot_instantiate_with_device_add
notation because we no longer call drive_get_next in the device
model.
Signed-off-by: Peter Maydell
---
hw/arm/xi
Turn the SD card into a QOM device.
This conversion only changes the device itself; the various
functions which are effectively methods on the device are not
touched at this point.
Signed-off-by: Peter Maydell
---
hw/sd/sd.c | 99 ++
in
Add a QOM bus for SD cards to plug in to.
Note that since sd_enable() is used only by one board and there
only as part of a broken implementation, we do not provide it in
the SDBus API (but instead add a warning comment about the old
function). Whoever converts OMAP and the nseries boards to QOM
w
This series attempts to QOMify sd.c (the actual SD card model),
including a proper QOM bus between the controller and the card.
This series removes the experimental x-drive property on sdhci-pci;
the syntax for using that device changes:
instead of using the x-drive property:
-device sdhci-pci
On Fri, 11 Dec 2015, Jan Beulich wrote:
> >>> On 11.12.15 at 15:33, wrote:
> > On Mon, 7 Dec 2015, Jan Beulich wrote:
> >> >>> On 07.12.15 at 15:56, wrote:
> >> > On Mon, 7 Dec 2015, Jan Beulich wrote:
> >> >> >>> On 07.12.15 at 13:45, wrote:
> >> >> > On Tue, 24 Nov 2015, Jan Beulich wrote:
> >
On Fri, 11 Dec 2015, Ian Campbell wrote:
> On Fri, 2015-12-11 at 14:26 +, Stefano Stabellini wrote:
> > On Wed, 9 Dec 2015, Ian Campbell wrote:
> > > On Thu, 2015-12-03 at 11:23 +, Ian Campbell wrote:
> > > > diff --git a/hw/display/xenfb.c b/hw/display/xenfb.c
> > > > index 5e324ef..c96d97
The following commits will remove support for the old sdhci-pci
command line syntax using the x-drive property:
-device sdhci-pci,x-drive=mydrive -drive id=mydrive,[...]
and replace it with an explicit sd device:
-device sdhci-pci -drive id=mydrive,[...] -device sd,drive=mydrive
(This is OK beca
On 11 December 2015 at 15:43, Max Reitz wrote:
> On 2015-12-11 at 16:40, Peter Maydell wrote:
>>
>> On 11 December 2015 at 15:30, Eric Blake wrote:
>>>
>>> On 12/11/2015 08:23 AM, Max Reitz wrote:
SQMP
-blockdev-remove-medium
+x-blockdev-remove-medium
---
On 12/11/2015 08:40 AM, Laszlo Ersek wrote:
> meta
>
> On 12/11/15 16:09, Thomas Huth wrote:
>> On 11/12/15 15:55, Samuel Thibault wrote:
>>> Thomas Huth, on Fri 11 Dec 2015 15:32:48 +0100, wrote:
So maybe it's better to do smaller steps instead: Would it for example
make sense to split
On 2015-12-11 at 16:40, Peter Maydell wrote:
On 11 December 2015 at 15:30, Eric Blake wrote:
On 12/11/2015 08:23 AM, Max Reitz wrote:
SQMP
-blockdev-remove-medium
+x-blockdev-remove-medium
--
Formatting nit, but not worth holding this up (as it is really our last
cha
Laszlo Ersek, on Fri 11 Dec 2015 16:40:32 +0100, wrote:
> > Sounds good, ... then I'd suggest to sent the preparation patches
> > separately next time and get them accepted first.
>
> And then the next reviewer will say, "nice, but it would be even nicer
> to see what *motivates* these preparatory
meta
On 12/11/15 16:09, Thomas Huth wrote:
> On 11/12/15 15:55, Samuel Thibault wrote:
>> Thomas Huth, on Fri 11 Dec 2015 15:32:48 +0100, wrote:
>>> So maybe it's better to do smaller steps instead: Would it for example
>>> make sense to split the whole series into two parts - first a series
>>> t
On 11 December 2015 at 15:30, Eric Blake wrote:
> On 12/11/2015 08:23 AM, Max Reitz wrote:
>>
>> SQMP
>> -blockdev-remove-medium
>> +x-blockdev-remove-medium
>> --
>
> Formatting nit, but not worth holding this up (as it is really our last
> chance to get it in 2.5 before bak
Peter and Sergey, Thank you so much for your help and explanation.
I appreciate your helps very much.
Sent from Mail for Windows 10
From: Sergey Fedorov
Sent: Friday, December 11, 2015 10:21 PM
To: Valerón JC;qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] How does TCG gen host code for a TB?
On 12/11/2015 08:23 AM, Max Reitz wrote:
> While in the long term we want throttling to be its own block filter
> BDS, in the short term we want it to be part of the BB instead of a BDS;
> even in the long term we may want legacy throttling to be automatically
> tied to the BB.
>
> blockdev-insert
On 11/12/15 01:15, Samuel Thibault wrote:
> From: Guillaume Subiron
>
> This patch simply adds a sa_family_t argument to remove the hardcoded
> "AF_INET" in the call of qemu_socket().
>
> Signed-off-by: Guillaume Subiron
> Signed-off-by: Samuel Thibault
> ---
> slirp/slirp.h | 2 +-
> sli
On Fri, 2015-12-11 at 14:26 +, Stefano Stabellini wrote:
> On Wed, 9 Dec 2015, Ian Campbell wrote:
> > On Thu, 2015-12-03 at 11:23 +, Ian Campbell wrote:
> > > diff --git a/hw/display/xenfb.c b/hw/display/xenfb.c
> > > index 5e324ef..c96d974 100644
> > > --- a/hw/display/xenfb.c
> > > +++ b
While in the long term we want throttling to be its own block filter
BDS, in the short term we want it to be part of the BB instead of a BDS;
even in the long term we may want legacy throttling to be automatically
tied to the BB.
blockdev-insert-medium and blockdev-remove-medium do not retain
thro
Hello Peter,
After having talked about the current status of the block layer today,
Markus, Kevin and me agreed to mark the newly introduced QMP commands
blockdev-insert-medium and blockdev-remove-medium experimental after
all (due to possible interference of its current status with future
designs
On 12/10/2015 05:11 PM, David Gibson wrote:
> The functions for migrating the hash page table on pseries machine type
> (htab_save_setup() and htab_load()) can report some errors with an
> explicit fprintf() before returning an appropriate eror code. Change these
> to use error_report() instead.
>
>>> On 11.12.15 at 15:33, wrote:
> On Mon, 7 Dec 2015, Jan Beulich wrote:
>> >>> On 07.12.15 at 15:56, wrote:
>> > On Mon, 7 Dec 2015, Jan Beulich wrote:
>> >> >>> On 07.12.15 at 13:45, wrote:
>> >> > On Tue, 24 Nov 2015, Jan Beulich wrote:
>> >> >> TBD: We probably need to deal with running on
On 12/10/2015 05:11 PM, David Gibson wrote:
> Use error_setg() to return an error instead of using an explicit exit().
>
> Signed-off-by: David Gibson
> ---
> hw/ppc/spapr.c | 9 +
> 1 file changed, 5 insertions(+), 4 deletions(-)
>
> +++ b/hw/ppc/spapr.c
> @@ -1107,6 +1107,7 @@ static
On 11/12/15 01:15, Samuel Thibault wrote:
> From: Guillaume Subiron
>
> A sa_family_t is now passed in argument to udp_attach instead of using a
> hardcoded "AF_INET" to call qemu_socket().
>
> Signed-off-by: Guillaume Subiron
> Signed-off-by: Samuel Thibault
> ---
> slirp/ip_icmp.c | 2 +-
>
On 11/12/15 15:55, Samuel Thibault wrote:
> Thomas Huth, on Fri 11 Dec 2015 15:32:48 +0100, wrote:
>> So maybe it's better to do smaller steps instead: Would it for example
>> make sense to split the whole series into two parts - first a series
>> that does all the preparation and cleanup patches.
On 11/12/15 01:15, Samuel Thibault wrote:
> From: Guillaume Subiron
>
> This patch makes solookup() compatible with varying address families. Also,
> this function was only compatible with TCP. Having the socket list in
> argument, it is now compatible with UDP too. Finally, some optimization
> c
On 12/10/2015 05:11 PM, David Gibson wrote:
> The spapr_alloc_htab() and spapr_reset_htab() functions currently handle
> all errors with error_setg(&error_abort, ...). That's correct for
> spapr_reset_htab() - if anything goes wrong there, there's really nothing
> we can do about it. For spapr_al
Thomas Huth, on Fri 11 Dec 2015 15:32:48 +0100, wrote:
> So maybe it's better to do smaller steps instead: Would it for example
> make sense to split the whole series into two parts - first a series
> that does all the preparation and cleanup patches. And then once that
> has been reviewed and merg
On 12/10/2015 05:11 PM, David Gibson wrote:
> Currently spapr_cpu_init() is hardcoded to handle any errors as fatal.
> That works for now, since it's only called from initial setup where an
> error here means we really can't proceed.
>
> However, we'll want to handle this more flexibly for cpu hot
We don't want newlines embedded in error messages. This seems to be a common
problem with new code so let's try to catch it with checkpatch.
This does not catch the newline when it is in a multiline statement. This is
quite a bit more difficult and can be handled as follow on work.
Signed-off-by:
On 11/12/15 01:15, Samuel Thibault wrote:
> From: Guillaume Subiron
>
> This patch replaces foreign and local address/port couples in Socket
> structure by 2 sockaddr_storage which can be casted in sockaddr_in.
> Direct access to address and port is still possible thanks to some
> \#define, so re
On Mon, 7 Dec 2015, Jan Beulich wrote:
> >>> On 07.12.15 at 15:56, wrote:
> > On Mon, 7 Dec 2015, Jan Beulich wrote:
> >> >>> On 07.12.15 at 13:45, wrote:
> >> > On Tue, 24 Nov 2015, Jan Beulich wrote:
> >> >> Now that the hypervisor intercepts all config space writes and monitors
> >> >> changes
On 11/12/15 15:01, Samuel Thibault wrote:
> Just to explain.
>
> I'm fine with revamping the patches, provided that we eventually
> converge somewhere.
>
> What I'm afraid of is that splitting patches in yet more many pieces,
> revamping the code yet more (moving code into their own functions, et
On Wed, 9 Dec 2015, Ian Campbell wrote:
> On Thu, 2015-12-03 at 11:23 +, Ian Campbell wrote:
> > diff --git a/hw/display/xenfb.c b/hw/display/xenfb.c
> > index 5e324ef..c96d974 100644
> > --- a/hw/display/xenfb.c
> > +++ b/hw/display/xenfb.c
> > @@ -104,9 +104,8 @@ static int common_bind(struct
On 11.12.2015 06:43, Valerón JC wrote:
> I want to trace a bug in tcg, which for me, at some point, generate
> infinite loop TB chains, that's unexpected. and I've found the final
> TB(head, since they're chaining) which run in an infinite loop, and I
> know a very weird trick to 'disable' this bug
A server can respond different to both methods, or can block one of the two.
Signed-off-by: Boris Schrijver
Reviewed-by: John Snow
---
V2: Impovements over V1:
- Don't check for CURLE_WRITE_ERROR, on success CURLE_OK will be returned.
- Use CURLOPT_CUSTOMREQUEST instead of CURLOPT_HTTPGET.
---
On Wed, Dec 09, 2015 at 08:37:16PM +0100, Igor Mammedov wrote:
> On Tue, 8 Dec 2015 20:44:38 +0200
> Marcel Apfelbaum wrote:
> > On 12/08/2015 07:59 PM, Eduardo Habkost wrote:
> > > On Mon, Dec 07, 2015 at 05:39:29PM +0200, Marcel Apfelbaum wrote:
> > >> On 12/02/2015 03:47 AM, Eduardo Habkost wro
Just to explain.
I'm fine with revamping the patches, provided that we eventually
converge somewhere.
What I'm afraid of is that splitting patches in yet more many pieces,
revamping the code yet more (moving code into their own functions, etc.)
will only make the patch series look even bigger and
On 12/10/2015 05:11 PM, David Gibson wrote:
> Current ppc_set_compat() returns -1 for errors, and also (unconditionally)
> reports an error message. The caller in h_client_architecture_support()
> may then report it again using an outdated fprintf().
>
> Clean this up by using the modern error re
[adding qemu-devel; per http://wiki.qemu.org/Contribute/SubmitAPatch,
ALL patches must include qemu-devel, even if they are also copying other
sublists]
On 12/11/2015 01:40 AM, Boris Schrijver wrote:
> A server can respond different to both methods, or can block one of the two.
>
> Signed-off-by:
On 11/12/15 14:47, Samuel Thibault wrote:
> Thomas Huth, on Fri 11 Dec 2015 14:43:42 +0100, wrote:
>> Anyway, it's IMHO a somewhat strange way to structure a patch ... maybe
>> it would be nicer to do it in one go instead (after splitting off the
>> arp_requested renaming)?
>
> Please discuss abou
On 12/07/2015 08:55 PM, Eric Blake wrote:
> visit_start_struct() and visit_type_enum() had a 'kind' argument
> that was usually set to either the stringized version of the
> corresponding qapi type name, or to NULL (although some clients
> didn't even get that right). But nothing ever used the arg
On 11/12/15 14:43, Thomas Huth wrote:
> On 11/12/15 14:38, Thomas Huth wrote:
>> On 11/12/15 01:15, Samuel Thibault wrote:
>>> From: Guillaume Subiron
>>>
>>> Basically, this patch replaces "arp" by "resolution" every time "arp"
>>> means "mac resolution" and not specifically ARP.
>>>
>>> Some ind
1 - 100 of 156 matches
Mail list logo
