Save the unused page info into page bitmap. The virtio balloon
driver call this new API to get the unused page bitmap and send
the bitmap to hypervisor(QEMU) for speeding up live migration.
During sending the bitmap, some the pages may be modified and are
no free anymore, this inaccuracy can be cor
Define a new feature bit which supports a new virtual queue. This
new virtual qeuque is for information exchange between hypervisor
and guest. The VMM hypervisor can make use of this virtual queue
to request the guest do some operations, e.g. drop page cache,
synchronize file system, etc. And the V
The implementation of the current virtio-balloon is not very
efficient, the time spends on different stages of inflating
the balloon to 7GB of a 8GB idle guest:
a. allocating pages (6.5%)
b. sending PFNs to host (68.3%)
c. address translation (6.1%)
d. madvise (19%)
It takes about 4126ms for the
Support the request for vm's unused page information, response with
a page bitmap. QEMU can make use of this bitmap and the dirty page
logging mechanism to skip the transportation of these unused pages,
this is very helpful to speed up the live migration process.
Signed-off-by: Liang Li
Cc: Micha
Expose the function to get the max pfn, so it can be used in the
virtio-balloon device driver. Simply include the 'linux/bootmem.h'
is not enough, if the device driver is built to a module, directly
refer the max_pfn lead to build failed.
Signed-off-by: Liang Li
Cc: Andrew Morton
Cc: Mel Gorman
Add a new feature which supports sending the page information with
a bitmap. The current implementation uses PFNs array, which is not
very efficient. Using bitmap can improve the performance of
inflating/deflating significantly
The page bitmap header will used to tell the host some information
abo
This patch set contains two parts of changes to the virtio-balloon.
One is the change for speeding up the inflating & deflating process,
the main idea of this optimization is to use bitmap to send the page
information to host instead of the PFNs, to reduce the overhead of
virtio data transmission
Will allow faster notifications using a bitmap down the road.
balloon_pfn_to_page() can be removed because it's useless.
Signed-off-by: Liang Li
Signed-off-by: Michael S. Tsirkin
Cc: Paolo Bonzini
Cc: Cornelia Huck
Cc: Amit Shah
---
drivers/virtio/virtio_balloon.c | 22 --
On 10/21/16 04:10, Programmingkid wrote:
On Oct 20, 2016, at 8:56 AM, Paolo Bonzini wrote:
- Original Message -
From: "Daniel P. Berrange"
To: "Programmingkid"
Cc: "qemu-devel qemu-devel" , "Paolo Bonzini"
Sent: Thursday, October 20, 2016 10:30:26 AM
Subject: Re: [Qemu-devel] my a
On Fri, Oct 21, 2016 at 11:50:05AM +1100, David Gibson wrote:
[...]
> > > In my setup the VFIO registered two memory areas with one page of
> > > unregistered memory
> > > between them.
> > >
> > > When I'm calling memory_region_notify_iommu it calls the notifier function
> > > of VFIO twice
> >
On Fri, 21 Oct 2016 12:09:54 +1100
David Gibson wrote:
> On Fri, Oct 21, 2016 at 12:40:58AM +1100, Nicholas Piggin wrote:
> > On Thu, 20 Oct 2016 15:08:07 +0200
> > Cédric Le Goater wrote:
> >
> > > On 10/20/2016 08:59 AM, Nicholas Piggin wrote:
> > > > Signed-off-by: Nicholas Piggin
> > >
On 10/20/2016 12:07 PM, Pranith Kumar wrote:
On Thu, Oct 20, 2016 at 3:02 PM, Richard Henderson wrote:
On 10/20/2016 11:58 AM, Pranith Kumar wrote:
Indeed, I was looking at atomic-6 on github. atomic-7 is not there yet :)
I've rebased atomic-6 (no -7). It should be there.
Am I looking
This patch allows the instantiation of the vfio-hisi-hnsvf device
from the QEMU command line (-device vfio-hisi-hnsvf,host="").
A specialized device tree node is created for the guest, containing
compat, dma-coherent, reg and interrupts properties.
Signed-off-by: Rick Song
---
hw/arm/sysbus-fdt.
I tried other QXL drivers: 22.33.46.473.
These work (but have a older date: 2015-07-28.
17.54.59.923 have the date 2016-04-21.
I got them from this package:
http://depot.flexvdi.com/guest-tools/flexvdi-guest-tools-2.2.11.iso
Those provide something, which lets my window resize freely.
--
You r
The platform device class has become abstract. This
patch introduces a hisilicon hnsvf device that derives
from it.
Signed-off-by: Rick Song
---
hw/vfio/Makefile.objs | 1 +
hw/vfio/hisi-hnsvf.c | 56 +++
include/hw/vfio/vfio-hisi-hns
QXL driver version is 17.54.59.923
Commandline (git compiled today) is:
/usr/sbin/qemu-system-x86_64 -name guest=dc,debug-threads=on -S -object
secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-1-dc
/master-key.aes -machine pc-i440fx-2.7,accel=kvm,usb=off,vmport=off
,dump-guest-co
On Thu, Oct 20, 2016 at 10:11:15PM +0300, Aviv B.D. wrote:
[...]
> > > +static void vtd_iotlb_page_invalidate_notify(IntelIOMMUState *s,
> > > + uint16_t domain_id, hwaddr
> > addr,
> > > + uint8_t am)
> > > +{
>
On Fri, 21 Oct 2016 08:30:53 +0530
Kirti Wankhede wrote:
> On 10/21/2016 2:52 AM, Alex Williamson wrote:
> > On Fri, 21 Oct 2016 02:44:37 +0530
> > Kirti Wankhede wrote:
> >
> ...
>
> >>
> >> +extern const char *vfio_device_api_string(u32 flags);
> >> +
> >> struct pci_dev
Hello Again, finally I could get back to this, and..
I was finishing a patch creating the open+truncate+mmap+unlink mechanism on
files specified by "vhostlog" parameter of tap devices. Patch is done, problem
is that... looks like the "memfd" is only used for shared logs AND vhost-net
(used for
The correct (and draft) one:
http://pastebin.ubuntu.com/23357210/
Im passing vhostlog parameter as "hdev->log_filename" so it can be accessed
from net_init_tap()-> functions AND from vhost_dev_start()-> functions. This
way I don't have to change function prototypes anymore.
> On Oct 21, 2016, a
For historical reasons, building the /chosen node in the guest device tree
is split across several places and includes both parts which write the DT
sequentially and others which use random access functions.
This patch consolidates construction of the node into one place, using
random access funct
On 10/21/2016 2:52 AM, Alex Williamson wrote:
> On Fri, 21 Oct 2016 02:44:37 +0530
> Kirti Wankhede wrote:
>
...
>>
>> +extern const char *vfio_device_api_string(u32 flags);
>> +
>> struct pci_dev;
>> #ifdef CONFIG_EEH
>> extern void vfio_spapr_pci_eeh_open(struct
For historical reasons construction of the guest device tree in spapr is
divided between spapr_create_fdt_skel() which is called at init time, and
spapr_build_fdt() which runs at reset time. Over time, more and more
things have needed to be moved to reset time.
Previous cleanups mean the only thi
For historical reasons construction of the /rtas node in the device
tree (amongst others) is split into several places. In particular
it's split between spapr_create_fdt_skel(), spapr_build_fdt() and
spapr_rtas_device_tree_setup().
In fact, as well as adding the actual RTAS tokens to the device t
Currently the /hypervisor device tree node is constructed in
spapr_create_fdt_skel(). As part of consolidating device tree construction
to reset time, move it to a function called from spapr_build_fdt().
Signed-off-by: David Gibson
Reviewed-by: Thomas Huth
---
hw/ppc/spapr.c | 49 +
Currently the device tree node for the XICS interrupt controller is in
spapr_create_fdt_skel(). As part of consolidating device tree construction
to reset time, this moves it to a function called from spapr_build_fdt().
In addition we move the actual code into hw/intc/xics_spapr.c with the
rest o
Construction of the /vdevice node (and its children) is divided between
spapr_create_fdt_skel() (at init time), which creates the base node, and
spapr_populate_vdevice() (at reset time) which creates the nodes for each
individual virtual device.
This consolidates both into a single function called
The /event-sources device tree node is built from spapr_create_fdt_skel().
As part of consolidating device tree construction to reset time, this moves
it to spapr_build_fdt().
Signed-off-by: David Gibson
Reviewed-by: Thomas Huth
---
hw/ppc/spapr.c | 6 +++---
hw/ppc/spapr_events.c | 2
spapr_finalize_fdt() both finishes building the device tree for the guest
and loads it into guest memory. For future cleanups, it's going to be
more convenient to do these two things separately. The loading portion is
pretty trivial, so we move it inline into the caller, ppc_spapr_reset().
We al
Currently spapr_create_fdt_skel() takes a bunch of individual parameters
for various things it will put in the device tree. Some of these can
already be taken directly from sPAPRMachineState. This patch alters it so
that all of them can be taken from there, which will allow this code to
be moved
These values are used only within ppc_spapr_reset(), so just change them
to local variables.
Signed-off-by: David Gibson
Reviewed-by: Thomas Huth
Reviewed-by: Alexey Kardashevskiy
---
hw/ppc/spapr.c | 14 +++---
include/hw/ppc/spapr.h | 1 -
2 files changed, 7 insertions(+), 8
At each system reset, the pseries machine needs to load RTAS (the runtime
portion of the guest firmware) into the VM. This means copying
the actual RTAS code into guest memory, and also updating the device
tree so that the guest OS and boot firmware can locate it.
For historical reasons the copy
For historical reasons construction of the guest device tree in spapr
is divided between spapr_create_fdt_skel() which is called at init
time, and spapr_build_fdt() which runs at reset time. Over time, more
and more things have needed to be moved to reset time.
This series consolidates all the de
The flattened device tree passed to pseries guests contains a list of
reserved memory areas. Currently we construct this list early in
spapr_create_fdt_skel() as we sequentially write the fdt.
This will be inconvenient for upcoming cleanups, so this patch moves
the reserve map changes to the end
On 10/21/2016 01:19 AM, Xiao, Guangrong wrote:
>> On 10/19/2016 10:14 PM, Paolo Bonzini wrote:
>>> On 19/10/2016 15:39, Xiao Guangrong wrote:
>>>
>>>
>>> I understood that KVM side is safe, however, vfio side is independent
>>> with kvm and the user of usrdata can fetch kvm struct at any time,
>>
On 10/21/2016 01:12 AM, Alex Williamson wrote:
> On Thu, 20 Oct 2016 15:23:53 +0800
> Jike Song wrote:
>
>> On 10/18/2016 05:22 AM, Kirti Wankhede wrote:
>>> diff --git a/drivers/vfio/mdev/mdev_core.c b/drivers/vfio/mdev/mdev_core.c
>>> new file mode 100644
>>> index ..7db5ec164aeb
>>
On 2016年10月20日 12:53, Hailiang Zhang wrote:
On 2016/10/20 11:53, Jason Wang wrote:
On 2016年10月10日 11:49, Zhang Chen wrote:
On 10/10/2016 11:13 AM, Hailiang Zhang wrote:
Hi,
On 2016/10/10 10:52, Zhang Chen wrote:
On 09/30/2016 12:06 PM, zhanghailiang wrote:
find_and_check_chardev() u
On Oct 20, 2016, at 8:56 AM, Paolo Bonzini wrote:
>
>
> - Original Message -
>> From: "Daniel P. Berrange"
>> To: "Programmingkid"
>> Cc: "qemu-devel qemu-devel" , "Paolo Bonzini"
>>
>> Sent: Thursday, October 20, 2016 10:30:26 AM
>> Subject: Re: [Qemu-devel] my attempt at new QEMU
On 2016年10月19日 03:35, P J P wrote:
Hello Jason,
+-- On Thu, 11 Aug 2016, Dmitry Fleytman wrote --+
| Reviewed-by: Dmitry Fleytman
|
| > @@ -531,6 +531,7 @@ static void vmxnet3_complete_packet(VMXNET3State *s,
int qidx, uint32_t tx_ridx)
| >
| > VMXNET3_RING_DUMP(VMW_RIPRN, "TXC", qidx
On 2016年10月18日 22:27, Kevin Wolf wrote:
Am 18.10.2016 um 16:10 hat Dmitry Fleytman geschrieben:
> On 17 Oct 2016, at 01:35 AM, Kevin Wolf wrote:
>
> The e1000e emulation zeroes out any used rx descriptor and then writes a
> completely newly constructed value there. By doing this,
On 2016年10月18日 22:10, Dmitry Fleytman wrote:
On 17 Oct 2016, at 01:35 AM, Kevin Wolf wrote:
The e1000e emulation zeroes out any used rx descriptor and then writes a
completely newly constructed value there. By doing this, it doesn't only
update the write-back area of the descriptors (as it's
On 2016年10月17日 18:39, yue wrote:
hi, jasowang:
according to my test , the vm's network performance is just 20% of
physical ethernet, the thread of vhost easily eat up 100% cpu when under
pressure.
What's you configuration (e.g qemu cli, host and guest kernel versions
and network set
On 2016年10月17日 17:01, Dr. David Alan Gilbert wrote:
* Stefan Weil (s...@weilnetz.de) wrote:
On 10/14/16 10:25, Dr. David Alan Gilbert wrote:
* Stefan Weil (s...@weilnetz.de) wrote:
Instead of allocating a VMStateDescription for each NIC instance,
the code now uses a single constant VMStateDe
On Thu, Oct 20, 2016 at 09:03:04AM +0200, Thomas Huth wrote:
> On 20.10.2016 07:11, David Gibson wrote:
> > spapr_finalize_fdt() both finishes building the device tree for the guest
> > and loads it into guest memory. For future cleanups, it's going to be
> > more convenient to do these two things
On Fri, 21 Oct 2016 12:09:15 +1100
David Gibson wrote:
> On Thu, Oct 20, 2016 at 05:59:10PM +1100, Nicholas Piggin wrote:
> > Power ISA specifies ME bit handling for system reset interrupt:
> >
> > if the interrupt occurred while the thread was in power-saving
> > mode, set to 1; otherwi
On Thu, Oct 20, 2016 at 09:49:42AM +0200, Thomas Huth wrote:
> On 20.10.2016 07:12, David Gibson wrote:
> > For historical reasons, building the /chosen node in the guest device tree
> > is split across several places and includes both parts which write the DT
> > sequentially and others which use
The platform device class has become abstract. This
patch introduces a hisilicon hnsvf device that derives
from it.
Signed-off-by: Rick Song
---
hw/vfio/Makefile.objs | 1 +
hw/vfio/hisi-hnsvf.c | 56 +++
include/hw/vfio/vfio-hisi-hns
On 10/20/2016 07:24 PM, Ed Swierk wrote:
> Shortly after I start qemu 2.7.0 with a qcow2 disk image created with
> -o cluster_size=1048576, it prints the following and dies:
>
> block/qcow2.c:2451: qcow2_co_pwrite_zeroes: Assertion `head + count <=
> s->cluster_size' failed.
>
> I narrowed the pr
This patch allows the instantiation of the vfio-hisi-hnsvf device
from the QEMU command line (-device vfio-hisi-hnsvf,host="").
A specialized device tree node is created for the guest, containing
compat, dma-coherent, reg and interrupts properties.
Signed-off-by: Rick Song
---
hw/arm/sysbus-fdt.
The usual use model for the libqos PCI functions is to map a specific PCI
BAR using qpci_iomap() then pass the returned token into IO accessor
functions. This, and the fact that iomap() returns a (void *) which
actually contains a PCI space address, kind of suggests that the return
value from ioma
On Fri, Oct 21, 2016 at 11:56:34AM +1100, Nicholas Piggin wrote:
> On Thu, 20 Oct 2016 18:49:22 +0200
> Greg Kurz wrote:
>
> > On Thu, 20 Oct 2016 17:59:12 +1100
> > Nicholas Piggin wrote:
> >
> > > The H_SIGNAL_SYS_RESET hcall allows a guest CPU to raise a system
> > > reset exception on other
ide-test uses many explicit inb() / outb() operations for its IO, which
means it's not portable to non-x86 platforms. This cleans it up to use
the libqos PCI accessors instead.
Signed-off-by: David Gibson
---
tests/ide-test.c | 179 ---
1 file
ivshmem implements a block of shared memory in a PCI BAR. Currently our
test case accesses this using qtest_mem{read,write}. However, deducing
the correct addresses for these requires making assumptions about the
internel format returned by qpci_iomap(), along with some ugly casts.
This patch ch
Currently the libqos PCI layer includes accessor helpers for 8, 16 and 32
bit reads and writes. It's likely that we'll want 64-bit accesses in the
future (plenty of modern peripherals will have 64-bit reigsters). This
adds them.
For PIO (not MMIO) accesses on the PC backend, this is implemented
In the libqos PCI code we now have accessors both for registers (byte
significance preserving) and for streaming data (byte address order
preserving). These exist in both the interface for qtest drivers and in
the machine specific backends.
However, the register-style accessors aren't actually ne
On 2016年10月12日 17:52, Jiri Pirko wrote:
Wed, Oct 12, 2016 at 11:10:55AM CEST, ppan...@redhat.com wrote:
From: Prasad J Pandit
Rocker network switch emulator has test registers to help debug
DMA operations. While testing host DMA access, a buffer address
is written to register 'TEST_DMA_ADDR'
The usual model for PCI IO with libqos is to use qpci_iomap() to map a
specific BAR for a PCI device, then perform IOs within that BAR using
qpci_io_{read,write}*().
However, certain devices also have legacy PCI IO. In this case, instead of
(or as well as) being accessed via PCI BARs, the device
The PCI backends in libqos each supply an iomap() and iounmap() function
which is used to set up a specified PCI BAR. But PCI BAR allocation takes
place entirely within PCI space, so doesn't really need per-backend
versions. For example, Linux includes generic BAR allocation code used on
platform
The PCI IO space (aka PIO, aka legacy IO) and PCI memory space (aka MMIO)
are distinct address spaces by the PCI spec (although parts of one might be
aliased to parts of the other in some cases).
However, qpci_io_read*() and qpci_io_write*() can perform accesses to
either space depending on parame
On Tue, Oct 18, 2016 at 10:06:31AM +0200, Cédric Le Goater wrote:
> Hello,
>
> Here are a couple of changes removing duplicated code and modifying
> the remaining icp_ routines still using a 'XICSState *' as argument.
Applied to ppc-for-2.8, thanks.
>
> Thanks,
>
> C.
>
> Cédric Le Goater (3
On Thu, Oct 20, 2016 at 02:06:08PM -0600, Alex Williamson wrote:
> [cc +david]
>
> On Thu, 20 Oct 2016 22:17:18 +0300
> "Aviv B.D." wrote:
>
> > On Mon, Oct 17, 2016 at 7:07 PM, Alex Williamson > > wrote:
> >
> > > On Mon, 17 Oct 2016 18:44:21 +0300
> > > "Aviv B.D" wrote:
> > >
> > > > F
On Fri, Oct 21, 2016 at 12:40:58AM +1100, Nicholas Piggin wrote:
> On Thu, 20 Oct 2016 15:08:07 +0200
> Cédric Le Goater wrote:
>
> > On 10/20/2016 08:59 AM, Nicholas Piggin wrote:
> > > Signed-off-by: Nicholas Piggin
> > > ---
> > > target-ppc/excp_helper.c | 8 ++--
> > > 1 file changed,
Currently PCI memory (aka MMIO) space is accessed via a set of readb/writeb
style accessors. This is what we want for accessing discrete registers of
a certain size. However, there are a few cases where we instead need a
"bag of bytes" style streaming interface to PCI MMIO space. This can be
eit
The 'addr' parameter to qvirtio_config_read*() doesn't have a consistent
meaning: when using the virtio-pci versions, it's a full PCI space address,
but for virtio-mmio, it's an offset from the device's base mmio address.
This means that the callers need to do different things to calculate the
add
This series contains a number of cleanups to the libqos code for
accessing PCI devices, and to tests which use it.
The general aim is to improve the consistency of semantics across
functions, and reduce the amount of intimate knowledge of the libqos
PCI layer needed by tests.
This should make it
On Thu, Oct 20, 2016 at 05:59:10PM +1100, Nicholas Piggin wrote:
> Power ISA specifies ME bit handling for system reset interrupt:
>
> if the interrupt occurred while the thread was in power-saving
> mode, set to 1; otherwise not altered
>
> Signed-off-by: Nicholas Piggin
I've applied t
Avoid tco-test making assumptions about the internal format of the address
tokens passed to PCI IO accessors, by using the new qpci_legacy_iomap()
function.
Signed-off-by: David Gibson
Reviewed-by: Laurent Vivier
---
tests/tco-test.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -
On Thu, 20 Oct 2016 18:49:22 +0200
Greg Kurz wrote:
> On Thu, 20 Oct 2016 17:59:12 +1100
> Nicholas Piggin wrote:
>
> > The H_SIGNAL_SYS_RESET hcall allows a guest CPU to raise a system
> > reset exception on other CPUs in the same guest.
> >
>
> Actually on all CPUs or all-but-self CPUs or
Shortly after I start qemu 2.7.0 with a qcow2 disk image created with
-o cluster_size=1048576, it prints the following and dies:
block/qcow2.c:2451: qcow2_co_pwrite_zeroes: Assertion `head + count <=
s->cluster_size' failed.
I narrowed the problem to bdrv_co_do_pwrite_zeroes(), called by
bdrv_ali
On Thu, Oct 20, 2016 at 11:54:42AM +0200, Laurent Vivier wrote:
>
>
> On 20/10/2016 05:43, David Gibson wrote:
> > ide-test uses many explicit inb() / outb() operations for its IO, which
> > means it's not portable to non-x86 platforms. This cleans it up to use
> > the libqos PCI accessors inste
On Thu, 10/20 10:21, Andy Grover wrote:
> On 10/20/2016 07:30 AM, Fam Zheng wrote:
> > On Thu, 10/20 15:08, Stefan Hajnoczi wrote:
> > > If a corrupt image is able to execute arbitrary code in the qemu-tcmu
> > > process, does /dev/uio0 or the tcmu shared memory interface allow get
> > > root or ke
On Thu, 10/20 15:55, Huamin Chen wrote:
> Hi Fam
>
> Can you push your code to github? I am spoiled with git :)
Pushed:
https://github.com/famz/qemu qemu-tcmu
Fam
>
> Thanks
>
> Huamin
I've narrowed this down. In exec.c the address is reduced by
section->offset_within_address_space. However, half the time that seems to
be wrong.
For usart1 at 40011004 it is 40011000, a difference of 4 which signals a
usart write.
For usart2 at 40004404 it is 4c00, a difference of 3804 which
Instead of automatically starting jobs at creation time via backup_start
et al, we'd like to return a job object pointer that can be started
manually at later point in time.
For now, add the block_job_start mechanism and start the jobs
automatically as we have been doing, with conversions job-by-j
Refactor backup_start as backup_job_create, which only creates the job,
but does not automatically start it. The old interface, 'backup_start',
is not kept in favor of limiting the number of nearly-identical interfaces
that would have to be edited to keep up with QAPI changes in the future.
Caller
Add an explicit start field to specify the entrypoint. We already have
ownership of the coroutine itself AND managing the lifetime of the
coroutine, let's take control of creation of the coroutine, too.
This will allow us to delay creation of the actual coroutine until we
know we'll actually start
Cleaning up after we have deferred to the main thread but before the
transaction has converged can be dangerous and result in deadlocks
if the job cleanup invokes any BH polling loops.
A job may attempt to begin cleaning up, but may induce another job to
enter its cleanup routine. The second job,
From: Vladimir Sementsov-Ogievskiy
Though it is not intended to be reached through normal circumstances,
if we do not gracefully deconstruct the transaction QLIST, we may wind
up with stale pointers in the list.
The rest of this series attempts to address the underlying issues,
but this should f
Requires: [Qemu-devel] [PATCH 0/7] blockjobs: preliminary refactoring work, Pt 1
There are a few problems with transactional job completion right now.
First, if jobs complete so quickly they complete before remaining jobs
get a chance to join the transaction, the completion mode can leave well
kn
I have some reproducible-ish segfaults in qemu 2.7.0 (built from source)
running under ubuntu 16.04, on a quad-core i7 Mac Mini Server.
I can reproduce these problems on a different Mac Mini, and I also
replaced the RAM on mine, so I'm sure it's not hardware related.
It's somewhat painful to
According to comment 41, this bug has been fixed, so I'm setting the
status to "Fix released" now ... Vitalis, your problem from comment 46
sounds differently - if it still persists today, please open a new bug
ticket for this instead.
** Changed in: qemu
Status: New => Fix Released
--
Yo
On Fri, 21 Oct 2016 02:44:37 +0530
Kirti Wankhede wrote:
> On 10/21/2016 2:35 AM, Alex Williamson wrote:
> > On Fri, 21 Oct 2016 01:59:55 +0530
> > Kirti Wankhede wrote:
> >
> >> On 10/21/2016 1:04 AM, Alex Williamson wrote:
> >>> On Tue, 18 Oct 2016 02:52:10 +0530
> >>> Kirti Wankhede wro
On 10/20/2016 03:55 AM, Kevin Wolf wrote:
We have been complaining for a long time about how the floppy controller and
floppy drives are combined in a single qdev device and how this makes the
device awkward to work with because it behaves different from all other block
devices.
The latest rea
On 10/21/2016 2:35 AM, Alex Williamson wrote:
> On Fri, 21 Oct 2016 01:59:55 +0530
> Kirti Wankhede wrote:
>
>> On 10/21/2016 1:04 AM, Alex Williamson wrote:
>>> On Tue, 18 Oct 2016 02:52:10 +0530
>>> Kirti Wankhede wrote:
>>>
Function vfio_device_api_string() returns string based on f
From: "Aviv Ben-David"
Supports translation trials without reporting error to guest on
translation failure.
Signed-off-by: Aviv Ben-David
---
exec.c| 3 ++-
hw/i386/amd_iommu.c | 4 ++--
hw/i386/intel_iommu.c | 59 +--
hw/ppc/
From: "Aviv Ben-David"
Adds a list of registered vtd_as's to intel iommu state to save
iteration over each PCI device in a search of the corrosponding domain.
Signed-off-by: Aviv Ben-David
---
hw/i386/intel_iommu.c | 109 ++---
hw/i386/intel_iommu_i
From: "Aviv Ben-David"
* Advertize Cache Mode capability in iommu cap register.
This capability is controlled by "cache-mode" property of intel-iommu device.
To enable this option call QEMU with "-device intel-iommu,cache-mode=true".
* On page cache invalidation in intel vIOMMU, check if th
From: "Aviv Ben-David"
This capability asks the guest to invalidate cache before each map operation.
We can use this invalidation to trap map operations in the hypervisor.
Signed-off-by: Aviv Ben-David
---
hw/i386/intel_iommu.c | 5 +
hw/i386/intel_iommu_internal.h | 1 +
include/
On Fri, 21 Oct 2016 01:59:55 +0530
Kirti Wankhede wrote:
> On 10/21/2016 1:04 AM, Alex Williamson wrote:
> > On Tue, 18 Oct 2016 02:52:10 +0530
> > Kirti Wankhede wrote:
> >
> >> Function vfio_device_api_string() returns string based on flag set in
> >> vfio_device_info's flag. This should be
Quoting Stefan Weil (2016-10-20 14:24:38)
> Signed-off-by: Stefan Weil
Reviewed-by: Michael Roth
> ---
> qemu-ga.texi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/qemu-ga.texi b/qemu-ga.texi
> index 0e53bf6..4c7a8fd 100644
> --- a/qemu-ga.texi
> +++ b/qemu-ga.texi
On Thu, Oct 20, 2016 at 04:58:42PM +0200, Igor Mammedov wrote:
> Currently firmware uses 1 byte at 0x5F offset in RTC CMOS
> to get number of CPUs present at boot. However 1 byte is
> not enough to handle more than 255 CPUs. So add a new
> fw_cfg file that would allow QEMU to tell it.
> For compat
On 10/21/2016 1:04 AM, Alex Williamson wrote:
> On Tue, 18 Oct 2016 02:52:10 +0530
> Kirti Wankhede wrote:
>
>> Function vfio_device_api_string() returns string based on flag set in
>> vfio_device_info's flag. This should be used by vendor driver to get string
>> based on flag for device_api at
Alex,
Addressing your comments other than invalidation part.
On 10/20/2016 2:32 AM, Alex Williamson wrote:
> On Tue, 18 Oct 2016 02:52:04 +0530
> Kirti Wankhede wrote:
>
...
>> Tested by assigning below combinations of devices to a single VM:
>> - GPU pass through only
>> - vGPU device only
>>
Hi Drew,
On 15/07/16 14:00, Andrew Jones wrote:
> Signed-off-by: Andrew Jones
>
> ---
> v2: configure irqs as NS GRP1
> ---
> lib/arm/asm/arch_gicv3.h | 184 ++
> lib/arm/asm/gic-v3.h | 321
> +
> lib/arm/asm/gic.h
Quoting Stefan Weil (2016-10-20 14:36:32)
> The NSIS based installer currently does not install qemu-ga.
> It installs the executables and other files for the QEMU system emulation.
>
> Signed-off-by: Stefan Weil
Reviewed-by: Michael Roth
> ---
> Makefile | 2 +-
> 1 file changed, 1 insertion
On Thu, Oct 20, 2016 at 12:32 PM, Vishal Verma wrote:
> On 10/19, Dan Williams wrote:
>> The 4.9 kernel added support for sub-dividing PMEM. With this kernel
>> patch [1] on top of that baseline, the PMEM-sub-division support can be
>> enabled for QEMU-KVM and any other platforms that advertise b
[cc +david]
On Thu, 20 Oct 2016 22:17:18 +0300
"Aviv B.D." wrote:
> On Mon, Oct 17, 2016 at 7:07 PM, Alex Williamson > wrote:
>
> > On Mon, 17 Oct 2016 18:44:21 +0300
> > "Aviv B.D" wrote:
> >
> > > From: "Aviv Ben-David"
> > >
> > > * Advertize Cache Mode capability in iommu cap registe
Hi All,
I have analysed my code and added the usb configuration while spawning the
guest CMM. Unfortunately still the usb is not visible.
Could you please help me on this.
I added this config "-usb -usbdevice host:090c:1000 " . you can see in the
last but one line
Following is my config
/b
On Thu, 20 Oct 2016 14:43:09 +1100
David Gibson wrote:
> Currently PCI memory (aka MMIO) space is accessed via a set of readb/writeb
> style accessors. This is what we want for accessing discrete registers of
> a certain size. However, there are a few cases where we instead need a
> "bag of byt
The NSIS based installer currently does not install qemu-ga.
It installs the executables and other files for the QEMU system emulation.
Signed-off-by: Stefan Weil
---
Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Makefile b/Makefile
index 3bcb056..69595ad 100644
--
1 - 100 of 395 matches
Mail list logo
