Am 06.04.2016 um 19:57 hat Max Reitz geschrieben:
> Its only caller is blk_new_open(), so we can just inline it there.
>
> Signed-off-by: Max Reitz
Maybe mention that this isn't pure code motion, but that you switch to a
bdrv_open() call with a NULL BDS. Either way:
Am 06.04.2016 um 19:57 hat Max Reitz geschrieben:
> The only caller of bdrv_close() left is bdrv_delete(). We may as well
> assert that, in a way (there are some things in bdrv_close() that make
> more sense under that assumption, such as the call to
> bdrv_release_all_dirty_bitmaps() which in
From: Corey Minyard
Signed-off-by: Corey Minyard
---
tests/acpi-test-data/pc/DSDT.ipmikcs | Bin 0 -> 5683 bytes
tests/acpi-test-data/q35/DSDT.ipmibt | Bin 0 -> 8456 bytes
tests/bios-tables-test.c | 58 ---
On 04/07/2016 05:35 AM, Alex Bligh wrote:
> * Call out TLS into a separate section
>
> * Add details of the TLS protocol itself
>
> * Emphasise that actual TLS session initiation (i.e. the TLS handshake) can
> be initiated from either side (as required by the TLS standard I believe
> and as
On 7 April 2016 at 12:04, Samuel Thibault wrote:
> The following changes since commit 7acbff99c6c285b3070bf0e768d56f511e2bf346:
>
> Update version for v2.6.0-rc1 release (2016-04-05 21:53:18 +0100)
>
> are available in the git repository at:
>
>
On Wed 06 Apr 2016 07:57:07 PM CEST, Max Reitz wrote:
> bdrv_append_temp_snapshot() uses bdrv_new() to create an empty BDS
> before invoking bdrv_open() on that BDS. This is probably a relict from
> when it used to do some modifications on that empty BDS, but now that is
> unnecessary, so we can
Am 06.04.2016 um 19:57 hat Max Reitz geschrieben:
> By now it has become just a wrapper around bdrv_new() and it has only a
> single user. Use bdrv_new() there instead and drop this function.
>
> Signed-off-by: Max Reitz
> Reviewed-by: Alberto Garcia
The
From: Prasad J Pandit
When receiving packets over Stellaris ethernet controller, it
uses receive buffer of size 2048 bytes. In case the controller
accepts large(MTU) packets, it could lead to memory corruption.
Add check to avoid it.
Reported by: Oleksandr Bazhaniuk
On 04/06/2016 11:48 PM, Michael S. Tsirkin wrote:
> On Wed, Apr 06, 2016 at 04:56:12PM -0700, Stefano Stabellini wrote:
>> On Sun, 3 Apr 2016, Michael S. Tsirkin wrote:
>>> piix3_ide_xen_class_init is identical to piix3_ide_class_init
>>> except it's buggy as it does not set exit and does not
From: Corey Minyard
Use the new ACPI table construction tools to create an ACPI
entry for IPMI. This adds a function called from build_dsdt
to add an DSDT entry for IPMI if IPMI is compiled in and has
registered firmware. It also adds a dummy function if IPMI
is not
On 07/04/2016 17:35, Pavel Borzenkov wrote:
> > On 05/04/2016 06:05, Kevin Wolf wrote:
> > > The options I can think of is adding a request field "max number of
> > > descriptors" or a flag "only single descriptor" (with the assumption
> > > that clients always want one or unlimited), but maybe
On Tue, 15 Mar 2016 00:02:48 +0800
Jevon Qiao wrote:
> Ceph as a promising unified distributed storage system is widely used in the
> world of OpenStack. OpenStack users deploying Ceph for block (Cinder) and
> object (S3/Swift) are unsurprisingly looking at Manila and CephFS
Eric,
(this crossed with v2)
On 7 Apr 2016, at 16:35, Eric Blake wrote:
> On 04/07/2016 06:36 AM, Alex Bligh wrote:
>>
>> On 7 Apr 2016, at 13:13, Alex Bligh wrote:
>>
>>> I guess it's worth documenting
>>> this, though I thought it was obvious.
>>
>>
On 7 Apr 2016, at 15:31, Eric Blake wrote:
>> +### TLS versions Certificates, authentication and authorisation
>
> s/versions/versions,/ ?
ok
>> +
>> +NBD implementations supporting TLS MUST support TLS version
>> +1.2, and MAY support other (earlier or later) versions of
On 07/04/2016 16:49, Peter Maydell wrote:
> > QOM to C++ classes
> I suspect if you looked at this you'd find that the QOM semantics
> for various things don't map onto C++ (ie that we have more runtime
> flexibility than C++ does).
True, but you don't have to use it. :) If your code is
Max Reitz writes:
> On 01.04.2016 17:57, Eric Blake wrote:
>> Commit 7836857 introduced a memory leak due to invalid use of
>> Error vs. visit_type_end(). If visiting the intermediate
>> members fails, we clear the error and unconditionally use
>> visit_end_struct() on the
* Call out TLS into a separate section
* Add details of the TLS protocol itself
* Emphasise that actual TLS session initiation (i.e. the TLS handshake) can
be initiated from either side (as required by the TLS standard I believe
and as actually works in practice)
* Clarify what is a
This RFC series follows on from discussions in the "Migrating decrementer"
thread relating to handling migration of the timebase and decrementer
registers for both TCG and KVM. The aim is to provide a consistent virtual
clock when migrating PPC machines TCG-TCG (already handled) and
KVM-KVM with
This requires that all -fw_cfg command line users use names of the form
opt/RFQDN/: such names are compatible with QEMU 2.4 and 2.5 as well as
future QEMU versions.
As ability to insert fw_cfg entries in QEMU root is useful for
firmware development, add a special prefix: unsupported/root/ that
P J P writes:
> From: Prasad J Pandit
>
> When receiving packets over MIPSnet network device, it uses
> receive buffer of size 1514 bytes. In case the controller
> accepts large(MTU) packets, it could lead to memory corruption.
> Add check to avoid
Stefan Hajnoczi writes:
> The patches fixes a single occurrence of a tab character that resulted
"The patch fixes" or "Fix", or drop the sentence.
> in mis-aligned indentation.
Really? It comes out aligned in my editor.
> Signed-off-by: Stefan Hajnoczi
Recalculate the tb_offset between the guest and host, applying it to all CPUs
when (re)starting the virtual machine. This has the effect of providing a
near-seamless virtual timebase for KVM guests that support
KVM_REG_PPC_TB_OFFSET.
Signed-off-by: Mark Cave-Ayland
Valerio Pachera writes:
> Hi, I'm interested about the option -writeconfig/-readconfig.
> I'm looking for some documentation about the format of the file, the
> syntax of all possible options and if there's a library that helps to
> read and write this file from external
On 04/07/2016 06:36 AM, Alex Bligh wrote:
>
> On 7 Apr 2016, at 13:13, Alex Bligh wrote:
>
>> I guess it's worth documenting
>> this, though I thought it was obvious.
>
> The next version will have this section:
>
> ### Downgrade attacks
>
> A danger inherent in any scheme
On 3 April 2016 at 14:05, Lluís Vilanova wrote:
> QOM to C++ classes
I suspect if you looked at this you'd find that the QOM semantics
for various things don't map onto C++ (ie that we have more runtime
flexibility than C++ does). This is just vaguely remembered from
On 29/03/2016 17:08, Kevin Wolf wrote:
> From: Max Reitz
>
> Passing -S 0 to qemu-img convert should result in all source data being
> copied to the output, even if that source data is known to be 0. The
> output image should therefore have exactly the same size on disk as
bdrv_pwrite_sync used to return zero or negative error, while blk_pwrite returns
the number of written bytes when successful. This caused VPC image creation
to fail spectacularly: it wrote the first 512 bytes, and then exited immediately
because of the non-zero answer from blk_pwrite. But the
Introduce PPCMachineClass in anticipation of making it the superclass for
all PPC machines.
Signed-off-by: Mark Cave-Ayland
---
hw/ppc/ppc.c| 16
include/hw/ppc/ppc.h| 16
include/qemu/typedefs.h |2 ++
3
Using a new DEFINE_PPC_MACHINE macro, make sure that all PPC machines now
derive from
the new PPCMachineClass.
Signed-off-by: Mark Cave-Ayland
---
hw/ppc/e500plat.c |7 +--
hw/ppc/mac_newworld.c | 17 +++--
hw/ppc/mac_oldworld.c |
Signed-off-by: Mark Cave-Ayland
---
hw/ppc/ppc.c | 45 +++--
1 file changed, 7 insertions(+), 38 deletions(-)
diff --git a/hw/ppc/ppc.c b/hw/ppc/ppc.c
index 39e15b1..053e600 100644
--- a/hw/ppc/ppc.c
+++ b/hw/ppc/ppc.c
@@
On Tue, Apr 05, 2016 at 03:43:08PM +0200, Paolo Bonzini wrote:
>
>
> On 05/04/2016 06:05, Kevin Wolf wrote:
> > The options I can think of is adding a request field "max number of
> > descriptors" or a flag "only single descriptor" (with the assumption
> > that clients always want one or
On 04/07/2016 12:45 PM, Laurent Vivier wrote:
>
>
> On 07/04/2016 12:27, Cédric Le Goater wrote:
>> Hello Laurent,
>>
>> On 04/07/2016 11:13 AM, Laurent Vivier wrote:
>>>
>>>
>>> On 05/04/2016 04:17, David Gibson wrote:
From: Cédric Le Goater
From: Benjamin
From: Stefan Weil
Commit d38ea87ac54af64ef611de434d07c12dc0399216 cleaned the include
statements which resulted in a wrong order of assert.h and the definition
of NDEBUG in tci.c. Normally NDEBUG modifies the definition of the assert
macro, but here this definition comes too
On Thu, Apr 07, 2016 at 12:35:59PM +0100, Alex Bligh wrote:
> * Call out TLS into a separate section
>
> * Add details of the TLS protocol itself
>
> * Emphasise that actual TLS session initiation (i.e. the TLS handshake) can
> be initiated from either side (as required by the TLS standard I
+-- On Thu, 7 Apr 2016, Peter Maydell wrote --+
| > n -= 31;
| > s->np++;
|
| We should do this check before we increase s->np, because
| if we're going to bail out then we won't be putting this
| packet into the RX FIFO.
Ah, right.
| The datasheet for this chip says that we
Am 06.04.2016 um 19:57 hat Max Reitz geschrieben:
> There are no callers to bdrv_open() or bdrv_open_inherit() left that
> pass a pointer to a non-NULL BDS pointer as the first argument of these
> functions, so we can finally drop that parameter and just make them
> return the new BDS.
>
>
* Michael S. Tsirkin (m...@redhat.com) wrote:
> On Thu, Apr 07, 2016 at 12:09:52PM +0100, Dr. David Alan Gilbert wrote:
> > * Eric Blake (ebl...@redhat.com) wrote:
> > > On 11/12/2015 12:56 PM, Dr. David Alan Gilbert wrote:
> > >
> > > >> One thing I still can't understand, why the unit test in
On 07/04/2016 14:54, Michael S. Tsirkin wrote:
>
> char check_zero(char *p, int len)
> {
> char res = 0;
> int i;
>
> for (i = 0; i < len; i++) {
> res = res | p[i];
> }
>
> return res;
> }
>
>
> If you compile this function with --tree-vectorize and
On Thu, Apr 07, 2016 at 09:12:57AM -0500, miny...@acm.org wrote:
> This patch set includes the fw_config file list sorting, which seems
> to have kind of stalled.
v5 is in my tree but I'll replace it with v6.
> Changes from v5:
>
> Added a check to rom_[re]set_order_override() functions to see
Lluís Vilanova writes:
> Markus Armbruster writes:
>
>> Peter Maydell writes:
>> [...]
>>> if we move away from C I'd rather
>>> it to be a language that's nicer than C rather than one that's
>>> uglier and larger and still retains all of C's
Am 06.04.2016 um 19:57 hat Max Reitz geschrieben:
> bdrv_append_temp_snapshot() uses bdrv_new() to create an empty BDS
> before invoking bdrv_open() on that BDS. This is probably a relict from
> when it used to do some modifications on that empty BDS, but now that is
> unnecessary, so we can just
On Thu, Apr 07, 2016 at 12:09:52PM +0100, Dr. David Alan Gilbert wrote:
> * Eric Blake (ebl...@redhat.com) wrote:
> > On 11/12/2015 12:56 PM, Dr. David Alan Gilbert wrote:
> >
> > >> One thing I still can't understand, why the unit test in host
> > >> environment shows
> > >> 'memcmp()' have
From: Corey Minyard
This will let things in other files (like IPMI) build SMBIOS tables.
Signed-off-by: Corey Minyard
---
hw/smbios/smbios.c | 70 ---
hw/smbios/smbios_build.h | 77
This patch set includes the fw_config file list sorting, which seems
to have kind of stalled.
Changes from v5:
Added a check to rom_[re]set_order_override() functions to see if fw_cfg
is set. This could cause a crash in certain circumstances.
Regenerated the BIOS test tables for other changes.
Daniel,
On 7 Apr 2016, at 12:51, Daniel P. Berrange wrote:
> IMHO, we should not permit what you call OPTIONALTLS or SELECTIVETLS,
> because these open possibilities for a MITM to perform downgrade
> attacks, where the MITM runs TLS to the real server, but runs no-TLS
> to
On Thu, Apr 07, 2016 at 11:09:48AM +, Ilya Maximets wrote:
> > --- Original Message ---
> > Sender : Michael S. Tsirkin
> > Date : Apr 07, 2016 10:01 (GMT+03:00)
> > Title : Re: Re: [PATCH 0/4] Fix QEMU crash on vhost-user socket disconnect.
> >
> > On Wed, Apr 06,
From: Sergey Fedorov
Signed-off-by: Sergey Fedorov
Signed-off-by: Sergey Fedorov
---
pc-bios/s390-ccw/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/pc-bios/s390-ccw/Makefile
Am 06.04.2016 um 19:57 hat Max Reitz geschrieben:
> bdrv_close() now asserts that the BDS's refcount is 0, therefore it
> cannot have any parents and the bdrv_parent_cb_change_media() call is a
> no-op.
>
> Signed-off-by: Max Reitz
Reviewed-by: Kevin Wolf
On Thu, Apr 07, 2016 at 01:13:10PM +0100, Alex Bligh wrote:
> Daniel,
>
> On 7 Apr 2016, at 12:51, Daniel P. Berrange wrote:
>
> > IMHO, we should not permit what you call OPTIONALTLS or SELECTIVETLS,
> > because these open possibilities for a MITM to perform downgrade
> >
Until commit 1c778ef7 ("nbd: convert to using I/O channels for actual
socket I/O", 2016-02-16), nbd_wr_sync returned -EAGAIN this scenario.
nbd_reply_ready required these semantics because it has two conflicting
requirements:
1) if a reply can be received on the socket, nbd_reply_ready needs
to
On 7 April 2016 at 11:56, Vijay Kilari wrote:
> On Thu, Apr 7, 2016 at 3:41 PM, Peter Maydell
> wrote:
>> On 7 April 2016 at 10:58, wrote:
>>> From: Vijaya Kumar K
>>>
>>> utils
+Raghavendra G who implemented this option in write-behind, to this
upstream patch review discussion
Pranith
On 04/06/2016 06:50 PM, Kevin Wolf wrote:
Am 06.04.2016 um 15:10 hat Jeff Cody geschrieben:
On Wed, Apr 06, 2016 at 01:51:59PM +0200, Kevin Wolf wrote:
Am 06.04.2016 um 13:41 hat
On 7 April 2016 at 13:35, P J P wrote:
> From: Prasad J Pandit
>
> When receiving packets over Stellaris ethernet controller, it
> uses receive buffer of size 2048 bytes. In case the controller
> accepts large(MTU) packets, it could lead to memory
Daniel,
>> Could you describe how a downgrade attack might occur? It's
>> always open to the client to refuse to access an export (or
>> the server as a whole) unless TLS is negotiated, as I make
>> clear here (see last phrase).
>
> Right, so that's OK if the client is implementing FORCEDTLS.
On 04/07/2016 05:51 AM, Daniel P. Berrange wrote:
>> +
>> +There are four modes of operation for a server. The
>> +server MUST support one of these modes.
>> +
>> +* The server operates entirely without TLS ('NOTLS'); OR
>> +
>> +* The server makes TLS available (for all exports) and
>> + it is
* Call out TLS into a separate section
* Add details of the TLS protocol itself
* Emphasise that actual TLS session initiation (i.e. the TLS handshake) can
be initiated from either side (as required by the TLS standard I believe
and as actually works in practice)
* Clarify what is a
Good day,
I'm using qemu on a Windows host. One thing I stumbled over was missing
9p support. I thought it was because of missing (x)attr, but Stefan Weil
told me that 9p is supported only under Linux hosts.
I searched a bit and got following questions:
* are my following results right:
Am 06.04.2016 um 19:57 hat Max Reitz geschrieben:
> Now that throttling has been moved to the BlockBackend level, we do not
> need to create a BDS along with the BB in the I/O throttling test.
>
> Signed-off-by: Max Reitz
Reviewed-by: Kevin Wolf
On 7 Apr 2016, at 13:13, Alex Bligh wrote:
> I guess it's worth documenting
> this, though I thought it was obvious.
The next version will have this section:
### Downgrade attacks
A danger inherent in any scheme relying on the negotiation
of whether TLS should be employed
On Thu, Apr 07, 2016 at 01:44:55PM +0200, Paolo Bonzini wrote:
> Until commit 1c778ef7 ("nbd: convert to using I/O channels for actual
> socket I/O", 2016-02-16), nbd_wr_sync returned -EAGAIN this scenario.
> nbd_reply_ready required these semantics because it has two conflicting
> requirements:
>
On 4/7/2016 2:53 AM, Michael Roth wrote:
Quoting Denis V. Lunev (2016-04-06 00:43:30)
From: Yuriy Pudgorodskiy
Signed-off-by: Yuriy Pudgorodskiy
Signed-off-by: Denis V. Lunev
CC: Michael Roth
---
From: Gerd Hoffmann
Entries are inserted in filename order instead of being
appended to the end in case sorting is enabled.
This will avoid any future issues of moving the file creation
around, it doesn't matter what order they are created now,
the will always be in filename
From: Corey Minyard
This is the same place that the ACPI SSDT table gets added, so that
devices can add themselves to the SMBIOS table.
Signed-off-by: Corey Minyard
---
hw/i386/pc.c | 11 ++-
1 file changed, 6 insertions(+), 5 deletions(-)
From: Corey Minyard
Add an IPMI table entry to the SMBIOS.
Signed-off-by: Corey Minyard
Acked-by: Michael S. Tsirkin
---
default-configs/i386-softmmu.mak | 1 +
default-configs/x86_64-softmmu.mak | 1 +
hw/smbios/Makefile.objs
Quoting Yuriy Pudgorodskiy (2016-04-07 06:22:13)
> On 4/7/2016 2:53 AM, Michael Roth wrote:
> > Quoting Denis V. Lunev (2016-04-06 00:43:30)
> >> From: Yuriy Pudgorodskiy
> >>
> >> Signed-off-by: Yuriy Pudgorodskiy
> >> Signed-off-by: Denis V. Lunev
Quoting Denis V. Lunev (2016-04-06 00:43:29)
> Signed-off-by: Yuriy Pudgorodskiy
> Signed-off-by: Denis V. Lunev
> CC: Michael Roth
>
Thanks, applied to qga tree:
https://github.com/mdroth/qemu/commits/qga
Can confirm it
On 07/04/2016 13:04, Changlong Xie wrote:
> Hi all
>
> Recently during test COLO, i found sometimes the client goes to hung on
> Primary side. First i thought it maybe a COLO revelant issue, but after
> ton of tests i doubt that this maybe a NBD issue (athough i'm not sure).
> So i'd like to
Am 06.04.2016 um 19:57 hat Max Reitz geschrieben:
> If bdrv_open_inherit() creates a snapshot BDS and *pbs is NULL, that
> snapshot BDS should be returned instead of the BDS under it.
>
> To this end, bdrv_append_temp_snapshot() now returns the snapshot BDS
> instead of just appending it on top
Signed-off-by: Emilio G. Cota
---
include/qemu/compiler.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/include/qemu/compiler.h b/include/qemu/compiler.h
index 8f1cc7b..1978ddc 100644
--- a/include/qemu/compiler.h
+++ b/include/qemu/compiler.h
@@ -41,6 +41,8 @@
# define
This way we can acquire the lock with xchg+test, instead of test+xchg+test.
Most spinlocks should be uncontended so this should result in a ne
performance gain.
Before:
4ad957: eb 09 jmp4ad962
4ad959: 0f 1f 80 00 00 00 00nopl 0x0(%rax)
On 04/07/2016 12:32 PM, Alex Bligh wrote:
> * Call out TLS into a separate section
>
> * Add details of the TLS protocol itself
>
> * Emphasise that actual TLS session initiation (i.e. the TLS handshake) can
> be initiated from either side (as required by the TLS standard I believe
> and as
On 7 April 2016 at 17:50, Paolo Bonzini wrote:
> From: Hervé Poussineau
>
> This line has been added in commit ef74679a810fe6858f625b9d52b68cc3fc61eb3d
> with
> other initializations. However, scancode set 0 doesn't exist (only 1, 2, 3).
> This works
Signed-off-by: Emilio G. Cota
---
include/qemu/thread.h | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/include/qemu/thread.h b/include/qemu/thread.h
index 1aa843b..599965e 100644
--- a/include/qemu/thread.h
+++ b/include/qemu/thread.h
@@ -2,6 +2,7 @@
On 04/07/2016 10:50 AM, Paolo Bonzini wrote:
> From: Eric Blake
>
> nbd-server.c currently fails to handle unsupported options properly.
> If during option haggling the client sends an unknown request, the
> server kills the connection instead of letting the client try to
>
This adds commandline support for the logging level of the
gluster protocol driver, output to stdout. The option is 'debug',
e.g.:
-drive filename=gluster://192.168.15.180/gv2/test.qcow2,debug=9
Debug levels are 0-9, with 9 being the most verbose, and 0 representing
no debugging output. The
Am 07.04.2016 um 21:16 schrieb Stefan Weil:
> Am 07.04.2016 um 20:15 schrieb Richard Henderson:
>> On 04/07/2016 08:53 AM, Sergey Fedorov wrote:
>>> +/* Enable TCI assertions only when debugging TCG (and without NDEBUG
>>> defined).
>>> + * Without assertions, the interpreter runs much faster. */
* Call out TLS into a separate section
* Add details of the TLS protocol itself
* Emphasise that actual TLS session initiation (i.e. the TLS handshake) can
be initiated from either side (as required by the TLS standard I believe
and as actually works in practice)
* Clarify what is a
On 04/07/2016 10:19 AM, Emilio G. Cota wrote:
We are inconsistent with the type of tb->flags: usage varies loosely
between int and uint64_t. Settle to uint32_t everywhere, which is
superior to both: at least one target (aarch64) uses the most significant
bit in the u32, and uint64_t is wasteful.
This option is unused; besides, it bloats the struct when not needed.
Let's just let writers define their own locks elsewhere.
Reviewed-by: Alex Bennée
Signed-off-by: Emilio G. Cota
---
cpus.c | 2 +-
include/qemu/seqlock.h | 10
On 7 Apr 2016, at 21:29, Eric Blake wrote:
> Upstream NBD is documenting that servers MAY choose to operate
> in a conditional mode, where it is up to the client whether to
> use TLS. For qemu's case, we want to always be in FORCEDTLS
> mode, because of the risk of
Eric,
> Qemu's initial implementation of TLS in the client is binary (you either
> want TLS or plaintext; there's no way to connect to a server and then
> decide whether to upgrade to TLS - a plaintext client will never use TLS
> of an OPTIONALTLS server). In TLS mode, the client always sends
>
On Thu, Apr 07, 2016 at 13:19:22 -0400, Emilio G. Cota wrote:
> We are inconsistent with the type of tb->flags: usage varies loosely
> between int and uint64_t. Settle to uint32_t everywhere, which is
> superior to both: at least one target (aarch64) uses the most significant
> bit in the u32, and
See v1 for context:
https://lists.gnu.org/archive/html/qemu-devel/2016-04/msg00587.html
All patches in v2 are checkpatch-clean, except 05 (checkpatch should
be ignored for this one) and 06, which I took unmodified (later patches
fix those warnings while doing other things, anyway).
Note that
The following changes since commit 7acbff99c6c285b3070bf0e768d56f511e2bf346:
Update version for v2.6.0-rc1 release (2016-04-05 21:53:18 +0100)
are available in the git repository at:
git://github.com/bonzini/qemu.git tags/for-upstream
for you to fetch changes up to
On 7 Apr 2016, at 21:35, Eric Blake wrote:
> grammar tweak:
> s/ and either /, /
sigh. fixed. Remembered to add your Reviewed-by: tag too.
--
Alex Bligh
signature.asc
Description: Message signed with OpenPGP using GPGMail
On Thu, Apr 07, 2016 at 01:19:22PM -0400, Emilio G. Cota wrote:
> We are inconsistent with the type of tb->flags: usage varies loosely
> between int and uint64_t. Settle to uint32_t everywhere, which is
> superior to both: at least one target (aarch64) uses the most significant
> bit in the u32,
Hi Peter,
please pull the following fix for target-xtensa.
The following changes since commit a648c137383d84bc4f95696e5293978d9541a26e:
Merge remote-tracking branch 'remotes/kraxel/tags/pull-ui-20160309-1' into
staging (2016-03-10 02:51:14 +)
are available in the git repository at:
From: Aleksandar Markovic
V2 - Relevant CPU initialization code changes revisited for all platforms.
- In connection with .. and
. Mips instructions handling, decision on whether
pre-nan2008 or
From: Aleksandar Markovic
This patch modifies SoftFloat library so that it can be configured at
run-time in relation to the meaning of signaling NaN bit, while, at the
same time, strictly preserving its behavior on all existing platforms.
Background:
In
The return value is unused and I am not sure why it would be useful.
Reviewed-by: Fam Zheng
Signed-off-by: Paolo Bonzini
---
block/io.c | 8 ++--
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/block/io.c b/block/io.c
index
Do not call bdrv_drain_recurse twice in bdrv_co_drain. A small
tweak to the logic in Fam's patch, which is harmless since no
one implements bdrv_drain anyway. But better get it right.
Signed-off-by: Paolo Bonzini
---
v4: new
block/io.c | 35
Xiao Guangrong ran kvm-unit-tests on an actual machine with PKU and
found that it fails:
test pte.p pte.user pde.p pde.user pde.a pde.pse pkru.wd pkey=1 user write
efer.nx cr4.pke: FAIL: error code 27 expected 7
Dump mapping: address: 0x1234
--L4: 2ebe007
--L3: 2ebf007
--L2:
From: Eric Blake
The compiler is smart enough to optimize out 'if (0)', but won't
type-check our printfs if they are hidden behind #if.
Signed-off-by: Eric Blake
Message-Id: <1459913704-19949-3-git-send-email-ebl...@redhat.com>
Signed-off-by: Paolo Bonzini
From: Sergey Fedorov
Ensure direct jump patching in PPC is atomic by:
* limiting translation buffer size in 32-bit mode to be addressable by
Branch I-form instruction;
* using atomic_read()/atomic_set() for code patching.
Signed-off-by: Sergey Fedorov
On Wed, Apr 06, 2016 at 01:02:16PM +0200, Kevin Wolf wrote:
> [ Adding some CCs ]
>
> Am 06.04.2016 um 05:29 hat Jeff Cody geschrieben:
> > Upon receiving an I/O error after an fsync, by default gluster will
> > dump its cache. However, QEMU will retry the fsync, which is especially
> > useful
Extract the handling of io_plug "depth" from linux-aio.c and let the
main bdrv_drain loop do nothing but wait on I/O.
Like the two newly introduced functions, bdrv_io_plug and bdrv_io_unplug
now operate on all children. The visit order is now symmetrical between
plug and unplug, making it
On Thu, Apr 07, 2016 at 06:39:10PM +0200, Markus Armbruster wrote:
> Marcel Apfelbaum writes:
>
> > On 03/23/2016 01:56 PM, Markus Armbruster wrote:
> >> Wei Jiangang writes:
> >>
> >>> v1 -> v2:
> >>>
> >>> - Extract a separate bugfix patch
> >>> -
Until commit 1c778ef7 ("nbd: convert to using I/O channels for actual
socket I/O", 2016-02-16), nbd_wr_sync returned -EAGAIN this scenario.
nbd_reply_ready required these semantics because it has two conflicting
requirements:
1) if a reply can be received on the socket, nbd_reply_ready needs
to
From: Eric Blake
nbd-server.c currently fails to handle unsupported options properly.
If during option haggling the client sends an unknown request, the
server kills the connection instead of letting the client try to
fall back to something older. This is precisely what
From: Sergey Fedorov
Ensure direct jump patching in TCI is atomic by:
* naturally aligning a location of direct jump address;
* using atomic_read()/atomic_set() to load/store the address.
Signed-off-by: Sergey Fedorov
Signed-off-by: Sergey Fedorov
1 - 100 of 232 matches
Mail list logo