Hi,
> Either mlock account (because it's mlocked defacto), and get_user_pages
> won't do that for you.
>
> Or you write the full-blown userptr implementation, including mmu_notifier
> support (see i915 or amdgpu), but that also requires Christian Königs
> latest ->invalidate_mapping RFC for dma
Unregistering the display change listener looks like a pointless
excercise given we'll exit in a moment. When exiting qemu via
menu/file/quit this will not happen either. Just drop the code.
Also return TRUE unconditionally. This will tell gtk to ignore the
close request, so gtk will not start
The L2 and refcount caches have default sizes that can be overridden
using the l2-cache-size and refcount-cache-size (an additional
parameter named cache-size sets the combined size of both caches).
Unless forced by one of the aforementioned parameters, QEMU will set
the unspecified sizes so that
We have just reduced the refcount cache size to the minimum unless
the user explicitly requests a larger one, so we have to update the
documentation to reflect this change.
Signed-off-by: Alberto Garcia
Reviewed-by: Eric Blake
---
docs/qcow2-cache.txt | 31 ++-
1 fil
Hi,
we talked about this the other day, so here are the patches to change
the default cache sizes in qcow2.
Without this patch:
* refcount-cache-size = l2-cache-size / 4
unless otherwise specified by the user. This is wasteful, the refcount
cache is accessed sequentially during normal I/O, so
> -Original Message-
> From: Dr. David Alan Gilbert [mailto:dgilb...@redhat.com]
> Sent: Friday, March 9, 2018 7:59 PM
> To: Zhang, Yulei
> Cc: qemu-devel@nongnu.org; Tian, Kevin ;
> alex.william...@redhat.com; kwankh...@nvidia.com;
> zhen...@linux.intel.com
> Subject: Re: [Qemu-devel] [
> From: Max Filippov [mailto:jcmvb...@gmail.com]
> the commit b39e3f34c9de7ead6a11a74aa2de78baf41d81a7
> ("icount: fixed saving/restoring of icount warp timers") has changed
> something that made timers test for target/xtensa unstable.
> Specifically ccount_write case in the tests/tcg/xtensa/test_t
> [...]
> Personally, I think it's useful to consider not merely "do we
> have anybody actively maintaining this" (after all our x86 frontend
> is not exactly very well-loved!) but also "are there users of QEMU
> out there using it?" and "is this actually something that exists
> in the real world
Intel processor trace should be disabled when
CPUID.(EAX=14H,ECX=0H).ECX.[bit31] is set.
Generated packets which contain IP payloads will have LIP
values when this bit is set, or IP payloads will have RIP
values.
Currently, The information of CPUID 14H is constant to make
live migration safty and t
* Su Hang (suhan...@mails.ucas.ac.cn) wrote:
>
> Sincerely sorry for my negligence to cause this bug!
> I will fix it as quick as I can!
>
> Sorry again, I'm really ashamed about the mistake I have made.
No need to be ashamed; bugs happen!
Dave
> Su Hang
>
> > -Original Messages-
> >
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id: 20180313211441.5179-1-js...@redhat.com
Subject: [Qemu-devel] [PULL 00/13] Bitmaps patches
=== TEST SCRIPT BEGIN ===
#!/bin/bash
BASE=base
n=1
total=$(git log --oneline $BASE
On Wed, Mar 14, 2018 at 2:07 AM, Pavel Dovgalyuk wrote:
>> From: Max Filippov [mailto:jcmvb...@gmail.com]
>> the commit b39e3f34c9de7ead6a11a74aa2de78baf41d81a7
>> ("icount: fixed saving/restoring of icount warp timers") has changed
>> something that made timers test for target/xtensa unstable.
>>
> -Original Message-
> From: Max Filippov [mailto:jcmvb...@gmail.com]
> Sent: Wednesday, March 14, 2018 12:41 PM
> To: Pavel Dovgalyuk
> Cc: Pavel Dovgaluk; qemu-devel
> Subject: Re: regression in timer code?
>
> On Wed, Mar 14, 2018 at 2:07 AM, Pavel Dovgalyuk wrote:
> >> From: Max Fil
* Michael S. Tsirkin (m...@redhat.com) wrote:
> On Mon, Mar 12, 2018 at 05:21:04PM +, Dr. David Alan Gilbert (git) wrote:
> > From: "Dr. David Alan Gilbert"
> >
> > Allow other userfaultfd's to be registered into the fault thread
> > so that handlers for shared memory can get responses.
> >
Le 14/03/2018 à 10:09, Xuetao Guan a écrit :
>
>> [...]
>> Personally, I think it's useful to consider not merely "do we
>> have anybody actively maintaining this" (after all our x86 frontend
>> is not exactly very well-loved!) but also "are there users of QEMU
>> out there using it?" and "is this
On 14/03/2018 04:35, Peter Xu wrote:
> On Tue, Mar 13, 2018 at 05:15:41PM -0700, no-re...@patchew.org wrote:
>
> [...]
>
>> Your patch has style problems, please review. If any of these errors
>> are false positives report them to the maintainer, see
>> CHECKPATCH in MAINTAINERS.
>> Checking PAT
On Tue, 13 Mar 2018 18:29:10 +
Peter Maydell wrote:
> On 12 March 2018 at 22:34, Eduardo Habkost wrote:
> > The following changes since commit 6ceb1b51f05f9e1892d082960ed602dca7b6696e:
> >
> > Merge remote-tracking branch
> > 'remotes/kraxel/tags/audio-20180312-pull-request' into staging
On Wed, Mar 14, 2018 at 2:53 AM, Pavel Dovgalyuk wrote:
> icount is adjusted by icount_warp_rt when CPU sleeps.
> These adjustments may be different in different runs.
> And the first adjustment is performed at the start of the machine.
> Therefore "now" value includes non-deterministic component
On 12/03/2018 19:33, Alexey Gerasimenko wrote:
> xen_pci_slot_get_pirq --> xen_cmn_pci_slot_get_pirq
> xen_piix3_set_irq --> xen_cmn_set_irq
Don't abbrvt names, xen_hvm_ is a better prefix.
>
> +fprintf(stderr, "WARNING: guest domain attempted to use
> PIRQ%c "
> +
On 03/09/2018 03:46 PM, Kevin Wolf wrote:
This adds the .bdrv_co_create driver callback to qcow, which
enables image creation over QMP.
Signed-off-by: Kevin Wolf
---
qapi/block-core.json | 21 +-
block/qcow.c | 196 ++-
2 files ch
On Wed, Mar 14, 2018 at 06:16:18AM -0500, Eric Blake wrote:
> On 03/09/2018 03:46 PM, Kevin Wolf wrote:
> > This adds the .bdrv_co_create driver callback to qcow, which
> > enables image creation over QMP.
> >
> > Signed-off-by: Kevin Wolf
> > ---
> > qapi/block-core.json | 21 +-
> > blo
On Wed, 14 Mar 2018 11:48:46 +0100
Paolo Bonzini wrote:
>On 12/03/2018 19:33, Alexey Gerasimenko wrote:
>> xen_pci_slot_get_pirq --> xen_cmn_pci_slot_get_pirq
>> xen_piix3_set_irq --> xen_cmn_set_irq
>
>Don't abbrvt names, xen_hvm_ is a better prefix.
Agree, will rename xen_cmn_* to xen_hv
On 03/14/2018 05:12 AM, Paolo Bonzini wrote:
Checking PATCH 16/69: chardev: tcp: postpone async connection setup...
Checking PATCH 17/69: chardev: tcp: let TLS run on chardev context...
It seems that Dan's last patch is still missing in the pull
request:
http://patchwork.ozlabs.org/patch/8831
On Wed, Mar 14, 2018 at 06:30:33AM -0500, Eric Blake wrote:
> On 03/14/2018 05:12 AM, Paolo Bonzini wrote:
>
> > > > Checking PATCH 16/69: chardev: tcp: postpone async connection setup...
> > > > Checking PATCH 17/69: chardev: tcp: let TLS run on chardev context...
> > >
> > > It seems that Dan's
* Michael S. Tsirkin (m...@redhat.com) wrote:
> On Mon, Mar 12, 2018 at 05:20:55PM +, Dr. David Alan Gilbert (git) wrote:
> > From: "Dr. David Alan Gilbert"
> >
> > This set enables postcopy migration with shared memory to a vhost user
> > process.
> > It's based off current head.
> >
>
On 14/03/2018 12:30, Eric Blake wrote:
> On 03/14/2018 05:12 AM, Paolo Bonzini wrote:
>
Checking PATCH 16/69: chardev: tcp: postpone async connection setup...
Checking PATCH 17/69: chardev: tcp: let TLS run on chardev context...
>>>
>>> It seems that Dan's last patch is still missing in
From: "Dr. David Alan Gilbert"
Add a notifier chain for postcopy with a 'reason' flag
and an opportunity for a notifier member to return an error.
Call it when enabling postcopy.
This will initially used to enable devices to declare they're unable
to postcopy and later to notify of devices of s
From: "Dr. David Alan Gilbert"
Utility to give the offset of a host pointer within a RAMBlock
(assuming we already know it's in that RAMBlock)
Signed-off-by: Dr. David Alan Gilbert
Reviewed-by: Peter Xu
---
exec.c| 10 ++
include/exec/cpu-common.h | 1 +
2 files c
From: "Dr. David Alan Gilbert"
Add a vhost feature flag for postcopy support, and
use the postcopy notifier to check it before allowing postcopy.
Signed-off-by: Dr. David Alan Gilbert
Reviewed-by: Peter Xu
---
contrib/libvhost-user/libvhost-user.h | 2 ++
docs/interop/vhost-user.txt
From: "Dr. David Alan Gilbert"
The choice of call to discard a block is getting more complicated
for other cases. We use fallocate PUNCH_HOLE in any file cases;
it works for both hugepage and for tmpfs.
We use the DONTNEED for non-hugepage cases either where they're
anonymous or where they're p
From: "Dr. David Alan Gilbert"
Split the set_mem_table routines in both qemu and libvhost-user
because the postcopy versions are going to be quite different
once changes in the later patches are added. However, this patch
doesn't produce any functional change, just the split.
Signed-off-by: Dr.
From: "Dr. David Alan Gilbert"
Open a userfaultfd (on a postcopy_advise) and send it back in
the reply to the qemu for it to monitor.
Signed-off-by: Dr. David Alan Gilbert
Reviewed-by: Marc-André Lureau
---
contrib/libvhost-user/libvhost-user.c | 42 +--
contri
From: "Dr. David Alan Gilbert"
This set enables postcopy migration with shared memory to a vhost user
process.
It's based off current head.
Testing is mostly performed with dpdk, with corresponding modifications by
Maxime.
v6 is a rebase on top of Michael's PCI world; this took some merg
From: "Dr. David Alan Gilbert"
Use a flag on the RAMBlock to state whether it has the
UFFDIO_ZEROPAGE capability, use it when it's available.
This allows the use of postcopy on tmpfs as well as hugepage
backed files.
Signed-off-by: Dr. David Alan Gilbert
Reviewed-by: Peter Xu
---
exec.c
From: "Dr. David Alan Gilbert"
We need a better way, but at the moment we need the address of the
mappings sent back to qemu so it can interpret the messages on the
userfaultfd it reads.
This is done as a 3 stage set:
QEMU -> client
set_mem_table
mmap stuff, get addresses
client
From: "Dr. David Alan Gilbert"
Allow replies with fds (for postcopy)
Signed-off-by: Dr. David Alan Gilbert
Reviewed-by: Marc-André Lureau
---
contrib/libvhost-user/libvhost-user.c | 30 +-
1 file changed, 29 insertions(+), 1 deletion(-)
diff --git a/contrib/libvho
From: "Dr. David Alan Gilbert"
Wire up a notifier to send a VHOST_USER_POSTCOPY_ADVISE
message on an incoming advise.
Later patches will fill in the behaviour/contents of the
message.
Signed-off-by: Dr. David Alan Gilbert
Reviewed-by: Marc-André Lureau
---
contrib/libvhost-user/libvhost-user
From: "Dr. David Alan Gilbert"
Register the UFD that comes in as the response to the 'advise' method
with the postcopy code.
Signed-off-by: Dr. David Alan Gilbert
Reviewed-by: Marc-André Lureau
---
hw/virtio/vhost-user.c | 20 +++-
1 file changed, 19 insertions(+), 1 deletion(
From: "Dr. David Alan Gilbert"
Allow other userfaultfd's to be registered into the fault thread
so that handlers for shared memory can get responses.
Signed-off-by: Dr. David Alan Gilbert
Reviewed-by: Peter Xu
---
migration/migration.c| 6 ++
migration/migration.h| 2 +
migration/
From: "Dr. David Alan Gilbert"
Utility for testing the map when you already know the offset
in the RAMBlock.
Signed-off-by: Dr. David Alan Gilbert
Reviewed-by: Peter Xu
Reviewed-by: Marc-André Lureau
---
migration/ram.c | 5 +
migration/ram.h | 1 +
2 files changed, 6 insertions(+)
diff
From: "Dr. David Alan Gilbert"
Resolve fault addresses read off the clients UFD into RAMBlock
and offset, and call back to the postcopy code to ask for the page.
Signed-off-by: Dr. David Alan Gilbert
Reviewed-by: Peter Xu
Reviewed-by: Marc-André Lureau
---
hw/virtio/trace-events | 3 +++
hw
From: "Dr. David Alan Gilbert"
Notify the vhost-user slave on reception of the 'postcopy-listen'
event from the source.
Signed-off-by: Dr. David Alan Gilbert
Reviewed-by: Marc-André Lureau
Reviewed-by: Peter Xu
---
contrib/libvhost-user/libvhost-user.c | 19 +++
contrib/libvh
From: "Dr. David Alan Gilbert"
Stash the RAMBlock and offset for later use looking up
addresses.
Signed-off-by: Dr. David Alan Gilbert
---
hw/virtio/trace-events | 1 +
hw/virtio/vhost-user.c | 49 +
2 files changed, 50 insertions(+)
diff --git
From: "Dr. David Alan Gilbert"
Add a hook to allow a client userfaultfd to be 'woken'
when a page arrives, and a walker that calls that
hook for relevant clients given a RAMBlock and offset.
Signed-off-by: Dr. David Alan Gilbert
Reviewed-by: Peter Xu
Reviewed-by: Marc-André Lureau
---
migrat
From: "Dr. David Alan Gilbert"
When new regions are sent to the client using SET_MEM_TABLE, register
them with the userfaultfd.
Signed-off-by: Dr. David Alan Gilbert
Reviewed-by: Marc-André Lureau
---
contrib/libvhost-user/libvhost-user.c | 34 ++
1 file change
From: "Dr. David Alan Gilbert"
Wire up a call to VHOST_USER_POSTCOPY_END message to the vhost clients
right before we ask the listener thread to shutdown.
Signed-off-by: Dr. David Alan Gilbert
Reviewed-by: Marc-André Lureau
---
hw/virtio/trace-events | 2 ++
hw/virtio/vhost-user.c | 34 +
From: "Dr. David Alan Gilbert"
Now that we have the mechanisms in here, allow shared memory in a
postcopy.
Note that QEMU can't tell who all the users of shared regions are
and thus can't tell whether all the users of the shared regions
have appropriate support for postcopy. Those devices that
From: "Dr. David Alan Gilbert"
Provide a helper to be used by shared waker functions to request
shared pages from the source.
The last_rb pointer is moved into the incoming state since this
helper can update it as well as the main fault thread function.
Signed-off-by: Dr. David Alan Gilbert
Rev
From: "Dr. David Alan Gilbert"
Register a waker function in vhost-user code to be notified when
pages arrive or requests to previously mapped pages get requested.
Signed-off-by: Dr. David Alan Gilbert
Reviewed-by: Marc-André Lureau
---
hw/virtio/trace-events | 3 +++
hw/virtio/vhost-user.c |
From: "Dr. David Alan Gilbert"
Cause the vhost-user client to be woken up whenever:
a) We place a page in postcopy mode
b) We get a fault and the page has already been received
Signed-off-by: Dr. David Alan Gilbert
---
migration/postcopy-ram.c | 14 ++
migration/trace-events
> Le 14/03/2018 �� 10:09, Xuetao Guan a 茅crit��:
>>
>>> [...]
>>> Personally, I think it's useful to consider not merely "do we
>>> have anybody actively maintaining this" (after all our x86 frontend
>>> is not exactly very well-loved!) but also "are there users of QEMU
>>> out there using it?" and
From: "Dr. David Alan Gilbert"
Provide a helper to send a 'wake' request on a userfaultfd for
a shared process.
The address in the clients address space is specified together
with the RAMBlock it was resolved to.
Signed-off-by: Dr. David Alan Gilbert
Reviewed-by: Marc-André Lureau
---
migrati
From: "Dr. David Alan Gilbert"
Add some notes to the migration documentation for shared memory
postcopy.
Signed-off-by: Dr. David Alan Gilbert
Reviewed-by: Marc-André Lureau
---
docs/devel/migration.rst | 41 +
1 file changed, 41 insertions(+)
diff --g
From: "Dr. David Alan Gilbert"
Clear the area and turn off THP.
PROT_NONE the area until after we've userfault advised it
to catch any unexpected changes.
Signed-off-by: Dr. David Alan Gilbert
Reviewed-by: Marc-André Lureau
---
contrib/libvhost-user/libvhost-user.c | 47 ++
From: "Dr. David Alan Gilbert"
This message is sent just before the end of postcopy to get the
client to stop using userfault since we wont respond to any more
requests. It should close userfaultfd so that any other pages
get mapped to the backing file automatically by the kernel, since
at this
From: "Dr. David Alan Gilbert"
Align RAMBlocks to page size alignment, and adjust the merging code
to deal with partial overlap due to that alignment.
This is needed for postcopy so that we can place/fetch whole hugepages
when under userfault.
Signed-off-by: Dr. David Alan Gilbert
---
hw/virt
With the huge number of QEMU targets, a default configuration will take
a very long time to rebuild. When developing most code changes, it is
sufficient to test compilation with a single target - rebuilding all
targets just extends compile times while not detecting any new problems.
Developers wil
From: "Dr. David Alan Gilbert"
Tell QEMU we understand the protocol features needed for postcopy.
Signed-off-by: Dr. David Alan Gilbert
Reviewed-by: Marc-André Lureau
---
contrib/libvhost-user/libvhost-user.c | 33 +
1 file changed, 33 insertions(+)
diff --git
On 13 March 2018 at 21:55, Eric Blake wrote:
> On 03/13/2018 09:17 AM, Eric Blake wrote:
This builds and passes 'make check', so even though the OOB portion
depends on chardev fixes that are still pending a pull request from
Paolo, that dependence can only be observed at runtim
A new cpu model called "KNM" is added to model Knights Mill processors.
Compared to "Skylake-Server" cpu model, the following features are
added:
avx512_4vnniw avx512_4fmaps avx512pf avx512er avx512_vpopcntdq
and the following features are removed:
pcid invpcid clflushopt avx512d
On Wed, Mar 14, 2018 at 03:29:59PM +0800, Boqun Feng wrote:
> A new cpu model called "KNM" is added to model Knights Mill processors.
Why the obscure acryonym? Can't we just call it KnightsMill so it is
obvious what it is to everyone, as we've done for all other Intel
CPU model names in the past.
On Wed, Mar 14, 2018 at 03:26:31AM +0800, Luwei Kang wrote:
> Intel processor trace should be disabled when
> CPUID.(EAX=14H,ECX=0H).ECX.[bit31] is set.
> Generated packets which contain IP payloads will have LIP
> values when this bit is set, or IP payloads will have RIP
> values.
> Currently, The
Ping
On 02/19/2018 11:12 AM, Daniel Henrique Barboza wrote:
v5:
- removed a paragraph in the recently added qemu_register_wakeup_notifier
comment that was added. That paragraph was adding too much in-depth
information about the current design of the system_wakeup, making it
harder to understand
Hi Pankaj,
I have a prototype (new one for virtio-mem I was working on over the last
weeks) for exactly what you need. I basically factored out the notion of a
memory device. So also virtio devices can be memory devices and get recognized
e.g. in formerly known pc_dimm_get_free_address(), so it
This is a preparation for the coming feature of creating dynamically an XML
description for the ARM sysregs.
A register has ARM_CP_NO_GDB enabled will not be shown in the dynamic XML.
This bit is enabled automatically when creating CP_ANY wildcard aliases.
This bit could be enabled manually for any
The previous version:
http://patchwork.ozlabs.org/project/qemu-devel/list/?series=33190
Abdallah Bouassida (3):
target/arm: Add "ARM_CP_NO_GDB" as a new bit field for ARMCPRegInfo
type
target/arm: Add "_S" suffix to the secure version of a sysreg
target/arm: Add the XML dynamic generatio
Generate an XML description for the cp-regs.
Register these regs with the gdb_register_coprocessor().
Add arm_gdb_get_sysreg() to use it as a callback to read those regs.
Add a dummy arm_gdb_set_sysreg().
Signed-off-by: Abdallah Bouassida
---
gdbstub.c| 10
include/qom/cpu.h
This is a preparation for the coming feature of creating dynamically an XML
description for the ARM sysregs.
Add "_S" suffix to the secure version of sysregs that have both S and NS views
Replace (S) and (NS) by _S and _NS for the register that are manually defined,
so all the registers follow the
On Wed, Mar 14, 2018 at 02:03:19PM +0800, Wei Wang wrote:
> On 03/14/2018 10:53 AM, Michael S. Tsirkin wrote:
> > On Wed, Mar 14, 2018 at 10:43:01AM +0800, Wei Wang wrote:
> > > On 03/14/2018 12:49 AM, Michael S. Tsirkin wrote:
> > > > On Wed, Mar 07, 2018 at 08:34:24PM +0800, Wei Wang wrote:
> > >
We've seen a few reports of
(gdb) source /usr/share/qemu-kvm/dump-guest-memory.py
Traceback (most recent call last):
File "/usr/share/qemu-kvm/dump-guest-memory.py", line 19, in
UINTPTR_T = gdb.lookup_type("uintptr_t")
gdb.error: No type named uintptr_t.
This occurs when symbols haven
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id: 20180313173355.4468-1-laur...@vivier.eu
Subject: [Qemu-devel] [PULL 00/18] Linux user for 2.12 patches
=== TEST SCRIPT BEGIN ===
#!/bin/bash
BASE=base
n=1
total=$(git log --
CentOS 6 lacks a realpath binary on the base install, which makes
all iotests runs fail:
001 - output mismatch (see 001.out.bad)
./check: line 815: realpath: command not found
diff: missing operand after `/home/dummy/qemu/tests/qemu-iotests/001.out'
diff: Try `diff --help' for more informa
On Wed, Mar 14, 2018 at 02:50:44PM +0800, Wei Wang wrote:
> On 03/14/2018 10:51 AM, Michael S. Tsirkin wrote:
> > On Wed, Mar 14, 2018 at 10:41:36AM +0800, Wei Wang wrote:
> > > On 03/14/2018 12:35 AM, Michael S. Tsirkin wrote:
> > > > On Wed, Mar 07, 2018 at 08:34:25PM +0800, Wei Wang wrote:
> > >
Daniel P. Berrange wrote:
> On Wed, Mar 07, 2018 at 11:59:49AM +0100, Juan Quintela wrote:
>> It will be used to store the uri tcp_port parameter. This is the only
>> parameter than can change and we can need to be able to connect to it.
>>
>> Signed-off-by: Juan Quintela
>>
>> --
>> # TODO e
On 03/14/2018 09:38 AM, Eric Blake wrote:
CentOS 6 lacks a realpath binary on the base install, which makes
all iotests runs fail:
001 - output mismatch (see 001.out.bad)
./check: line 815: realpath: command not found
diff: missing operand after `/home/dummy/qemu/tests/qemu-iotests/001.o
Daniel P. Berrange wrote:
> On Wed, Mar 07, 2018 at 11:59:50AM +0100, Juan Quintela wrote:
>> We can set the port parameter as zero. This patch lets us know what
>> port the system was choosen for us. Now we can migrate to this place.
>>
>> Signed-off-by: Juan Quintela
>> +void migrate_set_po
"Dr. David Alan Gilbert" wrote:
> * Juan Quintela (quint...@redhat.com) wrote:
>> We set the x-multifd-page-count and x-multifd-channels.
>>
>> Signed-off-by: Juan Quintela
>
>
> This should probably go nearer the end of the series;
it is _much_ better here. It makes so much easier to test tha
This change set fixes two breaking changes that were introduced in the
Windows Insider SDK 17110. First, a change to the WHvGetCapability function
decl to include the 'out' WrittenSizeInBytes. Second, changes to the
WHvSetPartitionProperty function decl and WHV_PARTITION_PROPERTY structure
to direc
This fixes a breaking change to WHvGetCapability to include the 'out'
WrittenSizeInBytes introduced in Windows Insider SDK 17110.
This specifies on return the safe length to read into the WHV_CAPABILITY
structure passed to the call.
Signed-off-by: Justin Terry (VM)
---
configure |
This removes the additional call to WHvGetVirtualProcessorRegisters in
whpx_vcpu_post_run now that the WHV_VP_EXIT_CONTEXT is returned in all
WHV_RUN_VP_EXIT_CONTEXT structures.
Signed-off-by: Justin Terry (VM)
---
target/i386/whpx-all.c | 41 +++--
1 file cha
This fixes a breaking change to WHvSetPartitionProperty to pass the 'in'
PropertyCode on function invocation introduced in Windows Insider SDK 17110.
Usage of this indicates the PropertyCode of the opaque PropertyBuffer passed in
on function invocation.
Also fixes the removal of the PropertyCode p
* Juan Quintela (quint...@redhat.com) wrote:
> "Dr. David Alan Gilbert" wrote:
> > * Juan Quintela (quint...@redhat.com) wrote:
> >> We set the x-multifd-page-count and x-multifd-channels.
> >>
> >> Signed-off-by: Juan Quintela
> >
> >
> > This should probably go nearer the end of the series;
>
On 14.03.2018 15:21, Andrew Jones wrote:
> We've seen a few reports of
>
> (gdb) source /usr/share/qemu-kvm/dump-guest-memory.py
> Traceback (most recent call last):
>File "/usr/share/qemu-kvm/dump-guest-memory.py", line 19, in
> UINTPTR_T = gdb.lookup_type("uintptr_t")
> gdb.error: N
On Mon 12 Mar 2018 11:07:50 PM CET, Fabiano Rosas wrote:
> The quorum driver is not a protocol so it should implement bdrv_open
> instead of bdrv_file_open and not provide a protocol_name.
>
> Attempts to invoke this driver using protocol syntax
> (i.e. quorum:) will now fail gracefully:
>
> $ qe
On Mon 12 Mar 2018 11:07:51 PM CET, Fabiano Rosas wrote:
> The throttle driver is not a protocol so it should implement bdrv_open
> instead of bdrv_file_open and not provide a protocol_name.
>
> Attempts to invoke this driver using protocol syntax
> (i.e. throttle:) will now fail gracefully:
>
>
Add support for the two currently defined HWCAP bits on MIPS - R6 and
MSA.
Buglink: https://bugs.launchpad.net/qemu/+bug/1754372
Signed-off-by: James Cowgill
---
linux-user/elfload.c | 24
1 file changed, 24 insertions(+)
diff --git a/linux-user/elfload.c b/linux-user/e
Add support for the two currently defined HWCAP bits on MIPS - R6 and
MSA.
Buglink: https://bugs.launchpad.net/qemu/+bug/1754372
Signed-off-by: James Cowgill
---
This was resent because I think I messed up my email config. Apologies if you
receive this twice.
linux-user/elfload.c | 24 +
We've seen a few reports of
(gdb) source /usr/share/qemu-kvm/dump-guest-memory.py
Traceback (most recent call last):
File "/usr/share/qemu-kvm/dump-guest-memory.py", line 19, in
UINTPTR_T = gdb.lookup_type("uintptr_t")
gdb.error: No type named uintptr_t.
This occurs when symbols haven
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id: 20180314153121.23838-1-james.cowg...@mips.com
Subject: [Qemu-devel] [PATCH] linux-user: implement HWCAP bits on MIPS
=== TEST SCRIPT BEGIN ===
#!/bin/bash
BASE=base
n=1
tota
Patch:
https://lists.nongnu.org/archive/html/qemu-devel/2018-03/msg04399.html
** Changed in: qemu
Status: New => In Progress
** Changed in: qemu
Assignee: (unassigned) => James Cowgill (jcowgill)
--
You received this bug notification because you are a member of qemu-
devel-ml, which
Hi everybody,
I am a relatively new user of qemu block layer. I am interested in it mainly
because it looks very powerful and general and I am hoping to integrate it on
our product and to contribute to it for new usecases.
I have existing use cases where we work with a model of a disk process p
On 14/03/2018 15:52, Justin Terry (VM) wrote:
> This change set fixes two breaking changes that were introduced in the
> Windows Insider SDK 17110. First, a change to the WHvGetCapability function
> decl to include the 'out' WrittenSizeInBytes. Second, changes to the
> WHvSetPartitionProperty funct
This affects Ubuntu 16.04 as in #4
** Also affects: qemu (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1587065
Title:
btrfs qemu-ga - multipl
From: Aleksandar Rikalo
Add support for initial ramdisk loading for the Mips Boston board.
Signed-off-by: Aleksandar Rikalo
---
hw/mips/boston.c | 54 +-
1 file changed, 45 insertions(+), 9 deletions(-)
diff --git a/hw/mips/boston.c b/hw/mip
Le 14/03/2018 à 16:31, James Cowgill a écrit :
> Add support for the two currently defined HWCAP bits on MIPS - R6 and
> MSA.
>
> Buglink: https://bugs.launchpad.net/qemu/+bug/1754372
> Signed-off-by: James Cowgill
> ---
> This was resent because I think I messed up my email config. Apologies if
* Wei Wang (wei.w.w...@intel.com) wrote:
> Count the number of 1s in a bitmap starting from an offset.
>
> Signed-off-by: Wei Wang
> CC: Dr. David Alan Gilbert
> CC: Juan Quintela
> CC: Michael S. Tsirkin
Reviewed-by: Dr. David Alan Gilbert
> ---
> include/qemu/bitmap.h | 13 +
Hi
This is v6, it differest from the patches that I sent with previous
multifd post:
- Rename x-tcp-port to x-socket-address
This is more *complicated* that it looks as:
* it is a pointer, so I need to use QAPI_CLONE() to make info
migrate work
* this is an union of structs. In QAPI.
Signed-off-by: Juan Quintela
Reviewed-by: Dr. David Alan Gilbert
Reviewed-by: Peter Xu
---
tests/migration-test.c | 44 ++--
1 file changed, 42 insertions(+), 2 deletions(-)
diff --git a/tests/migration-test.c b/tests/migration-test.c
index 422bf1afdf..8
It will be used to store the uri parameter. We want this only for tcp,
so we don't set it for other uris. We need it to know what port is
migration running.
Signed-off-by: Juan Quintela
--
This used to be uri parameter, but it has so many troubles to
reproduce that it don't just make sense.
T
Signed-off-by: Juan Quintela
Reviewed-by: Peter Xu
---
tests/migration-test.c | 64 ++
1 file changed, 64 insertions(+)
diff --git a/tests/migration-test.c b/tests/migration-test.c
index 834cdf50f2..fd885ba909 100644
--- a/tests/migration-test.c
+
1 - 100 of 157 matches
Mail list logo
