On 08/03/2017 08:01, Fam Zheng wrote:
> Linux exposes a separate limit, /sys/block/.../queue/max_segments, which
> in the worst case can be more restrictive than BLKSECTGET (as they are
> two different things). Similar to the BLKSECTGET story, guests don't see
> this limit and send big requests w
On 03/08/2017 05:15 AM, Jason Wang wrote:
On 2017年03月08日 10:43, Peter Xu wrote:
On Tue, Mar 07, 2017 at 02:47:30PM +0200, Marcel Apfelbaum wrote:
On 03/07/2017 11:09 AM, Jason Wang wrote:
After commit 96a8821d2141 ("virtio: unbreak virtio-pci with IOMMU
after caching ring translations"), IOM
On 03/08/2017 04:43 AM, Peter Xu wrote:
On Tue, Mar 07, 2017 at 02:47:30PM +0200, Marcel Apfelbaum wrote:
On 03/07/2017 11:09 AM, Jason Wang wrote:
After commit 96a8821d2141 ("virtio: unbreak virtio-pci with IOMMU
after caching ring translations"), IOMMU was required to be created in
advance. T
Hi everybody,
what will be the next version of QEMU after 2.9? Will we go for a 2.10
(as I've seen it mentioned a couple of times on the mailing list
already), or do we dare to switch to 3.0 instead?
I personally dislike two-digit minor version numbers like 2.10 since the
non-experienced users
Hi Eric,
thank you for your comments. My answers are inlined.
On 08.03.2017 03:36, Eric Blake wrote:
>
> I'm just focusing on the QMP interface portion of this.
>
> Is any of this information...
>
>> This patch moves the logic of the rdmsr and wrmsr functions to helper.c and
>> replaces their
Auto-converge aims to accelerate migration by slowing down the
generation of dirty pages. But user doesn't know how to determine the
throttle value, so, a new item "inst-dirty-pages-rate" in "info migrate"
would be helpful for user's determination.
Signed-off-by: Chao Fan
---
v2:
Update the wa
- Original Message -
> From: "Marcel Apfelbaum"
> To: "Michael S. Tsirkin" , "Peter Xu"
> Cc: qemu-devel@nongnu.org, "Paolo Bonzini" , "yi l liu"
> , "Jintack Lim"
> , "Jason Wang" , "Alex
> Williamson"
> Sent: Thursday, March 2, 2017 7:24:44 AM
> Subject: Re: [PATCH v3] intel_iommu:
Am 08.03.2017 um 03:54 hat Eric Blake geschrieben:
> Available as a tag at:
> git fetch git://repo.or.cz/qemu/ericb.git nbd-blkdebug-v6
>
> v5 was:
> https://lists.gnu.org/archive/html/qemu-devel/2017-02/msg03042.html
>
> Since then:
> - Rebase to master
> - Pull in Dan's patch that splits test 9
On Wed, Mar 08, 2017 at 03:35:50AM -0500, Paolo Bonzini wrote:
[...]
> The ordering should be explicit in the command line. Since we do not have
> cycles, it should be possible.
Current QEMU should have no restriction on parameter ordering, right?
Or do we have any existing case that:
"$QEMU
On Wed, Mar 08, 2017 at 10:17:09AM +0200, Marcel Apfelbaum wrote:
[...]
>
> I am sorry I was not clear enough:
> If a device is added after the system is up (hotplug), we cannot depend on
> the "machine_done"
> event to enable "bus master".
> This is why we have
>if (qdev_hotplug)
>
- Original Message -
> From: "Jason Wang"
> To: "Paolo Bonzini" , m...@redhat.com,
> qemu-devel@nongnu.org
> Cc: pet...@redhat.com
> Sent: Wednesday, March 8, 2017 7:22:06 AM
> Subject: Re: [Qemu-devel] [PATCH] virtio: destroy region cache during reset
>
>
>
> On 2017年03月08日 11:21, J
On Tue, Mar 07, 2017 at 05:27:55PM -0800, ashish mittal wrote:
> Thanks! There is one more input I need some help with!
>
> VxHS network library opens a fixed number of connection channels to a
> given host, and all the vdisks (that connect to the same host) share
> these connection channels.
>
>
Am 08.03.2017 um 03:15 hat Dong Jia Shi geschrieben:
> A normal call for raw_open should always pass in a non-NULL @options,
> but for some certain cases (e.g. trying to applying snapshot on a RBD
> image), they call raw_open with a NULL @options right after the calling
> for raw_close.
>
> Let's
Am 28.02.2017 um 20:33 hat Vladimir Sementsov-Ogievskiy geschrieben:
> Currently backup to nbd target is broken, as nbd doesn't have
> .bdrv_get_info realization.
>
> Signed-off-by: Vladimir Sementsov-Ogievskiy
Thanks, applied to the block branch.
Kevin
On Wed, Mar 08, 2017 at 05:09:45PM +0800, Peter Xu wrote:
> On Wed, Mar 08, 2017 at 10:17:09AM +0200, Marcel Apfelbaum wrote:
>
> [...]
>
> >
> > I am sorry I was not clear enough:
> > If a device is added after the system is up (hotplug), we cannot depend on
> > the "machine_done"
> > event to
On Wed, 8 Mar 2017 11:18:27 +0800
Jason Wang wrote:
> On 2017年03月07日 18:16, Cornelia Huck wrote:
> > On Tue, 7 Mar 2017 16:47:58 +0800
> > Jason Wang wrote:
> >
> >> We don't destroy region cache during reset which can make the maps
> >> of previous driver leaked to a buggy or malicious driver
> Current QEMU should have no restriction on parameter ordering, right?
> Or do we have any existing case that:
>
> "$QEMU -parameter1 -parameter2"
>
> will work, while...
>
> "$QEMU -parameter2 -parameter1"
>
> won't work?
Well, we have. If you, for example, add a scsi disk, you have to
On Wed, 8 Mar 2017 14:22:06 +0800
Jason Wang wrote:
> On 2017年03月08日 11:21, Jason Wang wrote:
> >
> > On 2017年03月07日 18:55, Paolo Bonzini wrote:
> >>
> >> On 07/03/2017 09:47, Jason Wang wrote:
> >>> We don't destroy region cache during reset which can make the maps
> >>> of previous driver leake
* Kevin Wolf [2017-03-08 10:13:46 +0100]:
> Am 08.03.2017 um 03:15 hat Dong Jia Shi geschrieben:
> > A normal call for raw_open should always pass in a non-NULL @options,
> > but for some certain cases (e.g. trying to applying snapshot on a RBD
> > image), they call raw_open with a NULL @options
> -Original Message-
> From: Stefano Stabellini [mailto:sstabell...@kernel.org]
> Sent: 07 March 2017 19:14
> To: Paul Durrant
> Cc: xen-de...@lists.xenproject.org; qemu-devel@nongnu.org; Stefano
> Stabellini
> Subject: Re: [PATCH v4 5/5] xen: use libxendevicemodel when available
>
> O
On 7 March 2017 at 16:20, Markus Armbruster wrote:
> Actually, the command line option is the least part of this series.
> Its bulk is about building infrastructure and getting errors out of
> the JSON parser.
>
> The design of the command line interface was discussed here:
> Subject: Non-flat com
On 2017年03月08日 17:10, Paolo Bonzini wrote:
- Original Message -
From: "Jason Wang"
To: "Paolo Bonzini" , m...@redhat.com,
qemu-devel@nongnu.org
Cc: pet...@redhat.com
Sent: Wednesday, March 8, 2017 7:22:06 AM
Subject: Re: [Qemu-devel] [PATCH] virtio: destroy region cache during reset
On 2017年03月08日 17:19, Cornelia Huck wrote:
On Wed, 8 Mar 2017 11:18:27 +0800
Jason Wang wrote:
On 2017年03月07日 18:16, Cornelia Huck wrote:
On Tue, 7 Mar 2017 16:47:58 +0800
Jason Wang wrote:
We don't destroy region cache during reset which can make the maps
of previous driver leaked to a
On 2017年03月08日 17:30, Cornelia Huck wrote:
On Wed, 8 Mar 2017 14:22:06 +0800
Jason Wang wrote:
On 2017年03月08日 11:21, Jason Wang wrote:
On 2017年03月07日 18:55, Paolo Bonzini wrote:
On 07/03/2017 09:47, Jason Wang wrote:
We don't destroy region cache during reset which can make the maps
of pr
* Peter Maydell (peter.mayd...@linaro.org) wrote:
> On 7 March 2017 at 20:46, Dr. David Alan Gilbert wrote:
> > The real fun is that there doesn't seem to be anything that stops
> > two blocks having the same name!
>
> The memory region API says that the name is for debugging only,
> so the probl
On 2017年03月08日 16:17, Marcel Apfelbaum wrote:
On 03/08/2017 05:15 AM, Jason Wang wrote:
On 2017年03月08日 10:43, Peter Xu wrote:
On Tue, Mar 07, 2017 at 02:47:30PM +0200, Marcel Apfelbaum wrote:
On 03/07/2017 11:09 AM, Jason Wang wrote:
After commit 96a8821d2141 ("virtio: unbreak virtio-pci
and tests/test-arm-mptimer?
Laurent
On 07/03/2017 19:45, Eric Blake wrote:
> Ignore test executables when building in-tree:
> test-crypto-hmac introduced in commit 4fd460b
> test-aio-multithread introduced in commit 0c330a7
>
> Signed-off-by: Eric Blake
> ---
>
> Doesn't affect the built binar
On 8 March 2017 at 09:26, Thomas Huth wrote:
> But anyway, the more important thing that keeps me concerned is: Someone
> once told me that we should get rid of old parameters and interfaces
> (like HMP commands) primarily only when we're changing to a new major
> version number. As you all know,
On 2017年03月08日 16:35, Paolo Bonzini wrote:
- Original Message -
From: "Marcel Apfelbaum"
To: "Michael S. Tsirkin" , "Peter Xu"
Cc: qemu-devel@nongnu.org, "Paolo Bonzini" , "yi l liu"
, "Jintack Lim"
, "Jason Wang" , "Alex Williamson"
Sent: Thursday, March 2, 2017 7:24:44 AM
Subje
On Wed, 8 Mar 2017 17:51:22 +0800
Jason Wang wrote:
> On 2017年03月08日 17:19, Cornelia Huck wrote:
> > On Wed, 8 Mar 2017 11:18:27 +0800
> > Jason Wang wrote:
> >
> >> On 2017年03月07日 18:16, Cornelia Huck wrote:
> >>> On Tue, 7 Mar 2017 16:47:58 +0800
> >>> Jason Wang wrote:
> >>>
> We don't
On Wed, 8 Mar 2017 17:53:23 +0800
Jason Wang wrote:
> On 2017年03月08日 17:30, Cornelia Huck wrote:
> > On Wed, 8 Mar 2017 14:22:06 +0800
> > Jason Wang wrote:
> >> there may be even more. So you want to fix them all?
> > Obviously not speaking for Paolo, but I think the virtio core should
> > hav
On Wed, Mar 08, 2017 at 09:26:00AM +0100, Thomas Huth wrote:
>
> Hi everybody,
>
> what will be the next version of QEMU after 2.9? Will we go for a 2.10
> (as I've seen it mentioned a couple of times on the mailing list
> already), or do we dare to switch to 3.0 instead?
>
> I personally disli
On Tue, 7 Mar 2017 19:46:56 +
"Dr. David Alan Gilbert" wrote:
> We seem to have a couple of weird cases where we end up with
> RAMBlocks with no name; I think they'll badly confuse
> the migration code, but I don't quite understand how they're
> happening.
>
> 1) device_del e1000e
> 2) -obj
Since cpu-memory and memory have same address space,one malloced
memory is enough. This patch will skip memory malloc for memory
address space,which will reduce around 3M physical memory in heap.
Signed-off-by: Yang Zhong
---
memory.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
The pass-through VM make the host kernel panic when it shutdown.
I read the kernel code and find the reason of panic is :
BUG_ON(domain_type_is_vm_or_si(domain));
in domain_get_iommu function.
The normal logic does not come to this function, it should be return when
__intel_map_single call functi
To record block operations the drive,I use parameters as shown in Figure 1, it
succeed, but the whole process is very slow.
To replay block operations the drive,I use parameters as shown in Figure 2,
after entering the startup options, the system stay black screen.
I can't solve this problem, I
* Igor Mammedov (imamm...@redhat.com) wrote:
> On Tue, 7 Mar 2017 19:46:56 +
> "Dr. David Alan Gilbert" wrote:
>
> > We seem to have a couple of weird cases where we end up with
> > RAMBlocks with no name; I think they'll badly confuse
> > the migration code, but I don't quite understand how
This handler will be required by PowerPC machines using multiple ICS
objects, like this is the case for PowerNV. Also update the sPAPR
machine to use the new handler.
Signed-off-by: Cédric Le Goater
---
hw/intc/xics.c| 9 +++--
hw/ppc/spapr.c| 11 +++
include/hw/ppc/
Hello,
Here is a series adding support for the interrupt controller as found
on a POWER8 system. POWER9 uses a different interrupt controller
called XIVE, still to be worked on.
The initial patches are small extensions to the recently added
XICSFabric framework. The PowerNV machine is then extend
From: Benjamin Herrenschmidt
The OCC is an on-chip microcontroller based on a ppc405 core used
for various power management tasks. It comes with a pile of additional
hardware sitting on the PIB (aka XSCOM bus). At this point we don't
emulate it (nor plan to do so). However there is one facility w
From: Benjamin Herrenschmidt
It adds the Naples chip which supports proper LPC interrupts via the
LPC controller rather than via an external CPLD.
Signed-off-by: Benjamin Herrenschmidt
[clg: - updated for qemu-2.9
- ported on latest PowerNV patchset ]
Signed-off-by: Cédric Le Goater
Revi
This helper will be used to translate the server number of the XIVE
(which is a PIR) into an ICPState index number (which is a cpu index).
Signed-off-by: Cédric Le Goater
---
hw/intc/xics.c| 11 +++
hw/ppc/ppc.c | 16
include/hw/ppc/xics.h | 1 +
target
This provides to a PowerNV chip (POWER8) access to the Interrupt
Management area, which contains the registers of the Interrupt Control
Presenters of each thread. These are used to accept, return, forward
interrupts in the system.
This area is modeled with a per-chip container memory region holdin
and populate the device tree accordingly for the guest to start using
interrupts. This also links the ICP object to its associated CPUState
(only used by KVM to control the kernel vCPU).
Signed-off-by: Cédric Le Goater
---
hw/ppc/pnv.c | 55 ++
Like this is done for the sPAPR machine, we use a simple array under
the PowerNV machine to store the Interrupt Control Presenters (ICP)
objects, one for each vCPU. This array is indexed by 'cpu_index' of
the CPUState.
We use a list to hold the different Interrupt Control Sources (ICS)
objects, as
From: Benjamin Herrenschmidt
The PSI (Processor Service Interface) Controller is one of the engines
of the "Bridge" unit which connects the different interfaces to the
Power Processor.
This adds just enough of the PSI bridge to handle various on-chip and
the one external interrupt. The rest of P
From: "Dr. David Alan Gilbert"
The 'name' parameter to memory_region_init_* had been marked as debug
only, however vmstate_region_ram uses it as a parameter to
qemu_ram_set_idstr to set RAMBlock names and these form part of the
migration stream.
Signed-off-by: Dr. David Alan Gilbert
---
includ
"Dr. David Alan Gilbert" wrote:
> * Igor Mammedov (imamm...@redhat.com) wrote:
>> On Tue, 7 Mar 2017 19:46:56 +
>> "Dr. David Alan Gilbert" wrote:
>>
>> > We seem to have a couple of weird cases where we end up with
>> > RAMBlocks with no name; I think they'll badly confuse
>> > the migrati
On 03/08/2017 07:54 AM, Dr. David Alan Gilbert (git) wrote:
From: "Dr. David Alan Gilbert"
The 'name' parameter to memory_region_init_* had been marked as debug
only, however vmstate_region_ram uses it as a parameter to
qemu_ram_set_idstr to set RAMBlock names and these form part of the
migrati
On 03/08/2017 12:11 PM, Yang Zhong wrote:
Since cpu-memory and memory have same address space,one malloced
memory is enough. This patch will skip memory malloc for memory
address space,which will reduce around 3M physical memory in heap.
Signed-off-by: Yang Zhong
Reviewed-by: Philippe Mathieu
Hi,
> libvirt suffered similar lack of clarity around when to bump major version
> number as opposed to minor version. To address this we recently adopted the
> rule[1] that major version number changes have no relation to features. The
> major number is simply incremented at the start of each c
On 08.03.2017 11:03, Peter Maydell wrote:
> On 8 March 2017 at 09:26, Thomas Huth wrote:
>> But anyway, the more important thing that keeps me concerned is: Someone
>> once told me that we should get rid of old parameters and interfaces
>> (like HMP commands) primarily only when we're changing to
Hi Cédric,
On 03/08/2017 07:52 AM, Cédric Le Goater wrote:
This provides to a PowerNV chip (POWER8) access to the Interrupt
Management area, which contains the registers of the Interrupt Control
Presenters of each thread. These are used to accept, return, forward
interrupts in the system.
This
On Wed, Mar 08, 2017 at 12:22:24PM +0100, Thomas Huth wrote:
> On 08.03.2017 11:03, Peter Maydell wrote:
> > On 8 March 2017 at 09:26, Thomas Huth wrote:
> >> But anyway, the more important thing that keeps me concerned is: Someone
> >> once told me that we should get rid of old parameters and in
On 03/08/2017 08:05 AM, QingFeng Hao wrote:
>
>
> 在 2017/3/7 18:19, Halil Pasic 写道:
>>
>> On 03/07/2017 11:05 AM, Kevin Wolf wrote:
>>> Am 07.03.2017 um 10:54 hat Halil Pasic geschrieben:
On 03/07/2017 10:29 AM, Kevin Wolf wrote:
> Am 07.03.2017 um 03:53 hat QingFeng Hao geschrieb
On 08.03.2017 04:09, Richard Henderson wrote:
> On 03/08/2017 11:16 AM, Julian Kirsch wrote:
>> For instance, many modern x86-64 operating systems maintain access to
>> internal
>> data structures via the MSR_GSBASE/MSR_KERNELGSBASE MSRs. Giving
>> introspection utilities (such as a remotely attac
On 8 March 2017 at 11:54, Dr. David Alan Gilbert (git)
wrote:
> From: "Dr. David Alan Gilbert"
>
> The 'name' parameter to memory_region_init_* had been marked as debug
> only, however vmstate_region_ram uses it as a parameter to
> qemu_ram_set_idstr to set RAMBlock names and these form part of t
* Julian Kirsch (g...@kirschju.re) wrote:
> Provide read/write access to x86 model specific registers (MSRs) by means of
> two new HMP commands "msr-list" and "msr-set". The rationale behind this
> is to improve introspection capabilities for system virtualization mode.
> For instance, many modern
BlockLimits.max_transfer can be too high without this fix, guest will
encounter I/O error or even get paused with werror=stop or rerror=stop. The
cause is explained below.
Linux has a separate limit, /sys/block/.../queue/max_segments, which in
the worst case can be more restrictive than the BLKSEC
On Wed, Mar 08, 2017 at 01:33:45PM +1100, David Gibson wrote:
> On Tue, Mar 07, 2017 at 09:02:37AM -0300, Eduardo Habkost wrote:
> > On Tue, Mar 07, 2017 at 02:31:05PM +1100, David Gibson wrote:
> > > On Mon, Mar 06, 2017 at 08:47:52AM -0300, Eduardo Habkost wrote:
> > > > On Mon, Mar 06, 2017 at 1
There are some broken URLs in the qemu-doc which reference tools that
are not available at their original location anymore. Fortunately, they
have been mirrored to archive.org, so point to that location instead.
Signed-off-by: Thomas Huth
---
qemu-doc.texi | 10 +-
1 file changed, 5 inse
On 08/03/2017 13:13, Thomas Huth wrote:
> There are some broken URLs in the qemu-doc which reference tools that
> are not available at their original location anymore. Fortunately, they
> have been mirrored to archive.org, so point to that location instead.
>
> Signed-off-by: Thomas Huth
Reviewe
Am 08.03.2017 um 13:08 hat Fam Zheng geschrieben:
> BlockLimits.max_transfer can be too high without this fix, guest will
> encounter I/O error or even get paused with werror=stop or rerror=stop. The
> cause is explained below.
>
> Linux has a separate limit, /sys/block/.../queue/max_segments, whi
After 6e85fce0225f "dtc: Update requirement to v1.4.2" QEMU stopped
compiling in CentOS7:
In file included from /home/aik/p/qemu/dtc/libfdt/libfdt.h:54:0,
from /home/aik/p/qemu/device_tree.c:30:
/home/aik/p/qemu/dtc/libfdt/libfdt_env.h:64:0: error: "__bitwise" redefined
[-Werror]
> On Mar 8, 2017, at 1:13 AM, Daniel P. Berrange wrote:
>
>> On Tue, Mar 07, 2017 at 05:27:55PM -0800, ashish mittal wrote:
>> Thanks! There is one more input I need some help with!
>>
>> VxHS network library opens a fixed number of connection channels to a
>> given host, and all the vdisks (t
On 03/08/2017 11:16 AM, Peter Xu wrote:
On Wed, Mar 08, 2017 at 05:09:45PM +0800, Peter Xu wrote:
On Wed, Mar 08, 2017 at 10:17:09AM +0200, Marcel Apfelbaum wrote:
[...]
I am sorry I was not clear enough:
If a device is added after the system is up (hotplug), we cannot depend on the
"machin
On 03/08/2017 12:08 PM, Jason Wang wrote:
On 2017年03月08日 16:35, Paolo Bonzini wrote:
- Original Message -
From: "Marcel Apfelbaum"
To: "Michael S. Tsirkin" , "Peter Xu"
Cc: qemu-devel@nongnu.org, "Paolo Bonzini" , "yi l liu"
, "Jintack Lim"
, "Jason Wang" , "Alex Williamson"
Sen
On 03/08/2017 12:24 PM, Philippe Mathieu-Daudé wrote:
> Hi Cédric,
>
> On 03/08/2017 07:52 AM, Cédric Le Goater wrote:
>> This provides to a PowerNV chip (POWER8) access to the Interrupt
>> Management area, which contains the registers of the Interrupt Control
>> Presenters of each thread. These a
On Wed, Mar 08, 2017 at 04:28:19PM +0800, Chao Fan wrote:
> Auto-converge aims to accelerate migration by slowing down the
> generation of dirty pages. But user doesn't know how to determine the
> throttle value, so, a new item "inst-dirty-pages-rate" in "info migrate"
> would be helpful for user's
On Wed, Mar 08, 2017 at 11:59:11AM +, Dr. David Alan Gilbert wrote:
[...]
> > +MsrInfoList *qmp_msr_list(uint32_t msr_idx, Error **errp)
> > +{
> > +#ifdef TARGET_I386
> > +bool valid;
> > +X86CPU *cpu;
> > +CPUX86State *env;
> > +CPUState *cpu_state;
> > +MsrInfoList *head
On Wed, Mar 8, 2017 at 2:39 AM, Alex Bennée wrote:
>
> Pranith Kumar writes:
>
>> Hi Alex,
>>
>> On Tue, Mar 7, 2017 at 10:50 AM, Alex Bennée wrote:
>>> Hi,
>>>
>>> This is the latest iteration of fixes for problems introduced by
>>> MTTCG. Aside from the usual slew of addressing review comments
On 8 March 2017 at 13:49, Alexey Kardashevskiy wrote:
> After 6e85fce0225f "dtc: Update requirement to v1.4.2" QEMU stopped
> compiling in CentOS7:
>
> In file included from /home/aik/p/qemu/dtc/libfdt/libfdt.h:54:0,
> from /home/aik/p/qemu/device_tree.c:30:
> /home/aik/p/qemu/dtc
On 3 March 2017 at 15:58, Eduardo Habkost wrote:
> On Tue, Jan 31, 2017 at 02:11:59PM +0100, Thomas Huth wrote:
>> When running with KVM on POWER, we register some CPU types during
>> the initialization function of the ppc64 KVM code (which unfortunately
>> also can not be done via a type_init() l
On 7 March 2017 at 16:40, Kevin Wolf wrote:
> The following changes since commit ff79d5e939c38677a575e3493eb9b4d36eb21865:
>
> Merge remote-tracking branch 'remotes/xtensa/tags/20170306-xtensa' into
> staging (2017-03-07 09:57:14 +)
>
> are available in the git repository at:
>
>
> git://
On Wed, Mar 08, 2017 at 03:31:01PM +0100, Peter Maydell wrote:
> On 3 March 2017 at 15:58, Eduardo Habkost wrote:
> > On Tue, Jan 31, 2017 at 02:11:59PM +0100, Thomas Huth wrote:
> >> When running with KVM on POWER, we register some CPU types during
> >> the initialization function of the ppc64 KV
On 03/08/2017 04:00 AM, Laurent Vivier wrote:
> and tests/test-arm-mptimer?
Introduced in commit 882fac37. Looks like my usual subset build focusing
on x86 doesn't see it, but indeed an all-targets build shows it. I'll
spin a v2.
--
Eric Blake eblake redhat com+1-919-301-3266
Libvirt virtu
Ignore test executables when building in-tree:
test-arm-mptimer introduced in commit 882fac3
test-crypto-hmac introduced in commit 4fd460b
test-aio-multithread introduced in commit 0c330a7
Signed-off-by: Eric Blake
---
v2: pick up another built binary [Laurent]
Doesn't affect the built binaries
On 08/03/2017 16:15, Eric Blake wrote:
> Ignore test executables when building in-tree:
> test-arm-mptimer introduced in commit 882fac3
> test-crypto-hmac introduced in commit 4fd460b
> test-aio-multithread introduced in commit 0c330a7
>
> Signed-off-by: Eric Blake
Reviewed-by: Laurent Vivier
On 08.03.2017 12:59, Dr. David Alan Gilbert wrote:
> * Julian Kirsch (g...@kirschju.re) wrote:
>
> I'll leave those who know more about gdb to answer whether that's the best way
> of doing it; but I can see them being useful to those just trying to debug
> stuff from the monitor.
>
Just want to
On 08.03.2017 15:50, Eduardo Habkost wrote:
> On Wed, Mar 08, 2017 at 03:31:01PM +0100, Peter Maydell wrote:
>> On 3 March 2017 at 15:58, Eduardo Habkost wrote:
>>> On Tue, Jan 31, 2017 at 02:11:59PM +0100, Thomas Huth wrote:
When running with KVM on POWER, we register some CPU types during
>
On 07.03.2017 11:47, Kevin Wolf wrote:
> Am 06.03.2017 um 20:54 hat Max Reitz geschrieben:
>> For one thing, this allows us to drop the error message generation from
>> qemu-img.c and blockdev.c and instead have it unified in
>> bdrv_truncate().
>>
>> Signed-off-by: Max Reitz
>
>> block/commit.c
On Wed, Mar 8, 2017 at 8:29 AM, Markus Armbruster wrote:
> John Snow writes:
>
>> On 03/07/2017 03:16 AM, Markus Armbruster wrote:
>>> John Snow writes:
>>>
On 03/06/2017 03:18 AM, Markus Armbruster wrote:
> Nir Soffer writes:
>
>> On Fri, Mar 3, 2017 at 9:29 PM, John Snow wro
On 08.03.2017 14:57, Eduardo Habkost wrote:
>>
>> This should be abstracted some how so that we don't need
>> x86 specifics in cpus.c; perhaps just an architecture call
>> back on the CPU.
>
> If it's only supported by x86, I would just move the
> implementation to a x86-specific file, and add a
On Mon, Mar 06, 2017 at 09:09:48AM -0300, Eduardo Habkost wrote:
> Hi,
>
>
> On Sun, Mar 05, 2017 at 11:46:33PM +0200, Krzysztof Kozlowski wrote:
> > In few places the function arguments and local variables are not
> > modifying data passed through pointers so this can be made const for
> > code
On Tue, 7 Mar 2017 14:47:30 +0200
Marcel Apfelbaum wrote:
> On 03/07/2017 11:09 AM, Jason Wang wrote:
> > After commit 96a8821d2141 ("virtio: unbreak virtio-pci with IOMMU
> > after caching ring translations"), IOMMU was required to be created in
> > advance. This is because we can only get the c
On 07.03.2017 11:47, Kevin Wolf wrote:
> Am 06.03.2017 um 20:54 hat Max Reitz geschrieben:
>> For one thing, this allows us to drop the error message generation from
>> qemu-img.c and blockdev.c and instead have it unified in
>> bdrv_truncate().
>>
>> Signed-off-by: Max Reitz
>
>> block/commit.c
Public bug reported:
There is a project (https://github.com/narke/colorForth ) wich always
worked with qemu up to version 2.5.1.1 but doesn't works from version
2.6 onwards. It continues to work with bochs.
Downlaod: git clone https://github.com/narke/colorForth.git
Build: make
Test: qemu-system-
On 03/07/2017 07:36 PM, Dr. David Alan Gilbert (git) wrote:
> From: "Dr. David Alan Gilbert"
>
> Provide a helper to say whether a RAMBlock was created as a
> shared mapping.
>
> Signed-off-by: Dr. David Alan Gilbert
> ---
> exec.c| 5 +
> include/exec/cpu-common.h |
* Halil Pasic (pa...@linux.vnet.ibm.com) wrote:
>
>
> On 03/07/2017 07:36 PM, Dr. David Alan Gilbert (git) wrote:
> > From: "Dr. David Alan Gilbert"
> >
> > Provide a helper to say whether a RAMBlock was created as a
> > shared mapping.
> >
> > Signed-off-by: Dr. David Alan Gilbert
> > ---
>
Hi,
On 22/08/2016 18:17, Prem Mallappa wrote:
> v1 -> v2:
> - Adopted review comments from Eric Auger
> - Make SMMU_DPRINTF to internally call qemu_log
> (since translation requests are too many, we need control
>on the type of log we want)
On Wed, Mar 8, 2017 at 5:04 AM, Ketan Nilangekar
wrote:
>
>
>> On Mar 8, 2017, at 1:13 AM, Daniel P. Berrange wrote:
>>
>>> On Tue, Mar 07, 2017 at 05:27:55PM -0800, ashish mittal wrote:
>>> Thanks! There is one more input I need some help with!
>>>
>>> VxHS network library opens a fixed number o
On Wed, Mar 08, 2017 at 09:59:32AM -0800, ashish mittal wrote:
> On Wed, Mar 8, 2017 at 5:04 AM, Ketan Nilangekar
> wrote:
> >
> >
> >> On Mar 8, 2017, at 1:13 AM, Daniel P. Berrange wrote:
> >>
> >>> On Tue, Mar 07, 2017 at 05:27:55PM -0800, ashish mittal wrote:
> >>> Thanks! There is one more i
In order to use error_setg() and similar functions, we need to include
qapi/error.h.
Signed-off-by: Max Reitz
---
block/archipelago.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/block/archipelago.c b/block/archipelago.c
index 2449cfc702..01c4ff2f7d 100644
--- a/block/archipelago.c
+++ b/
Hello all,
I just found that there is a significant performance difference between
QEMU version 2.2.0 and 2.6.0.
Here are the execution times of the benchmark 458.sjeng from SPEC CINT2006
with test workload using user only emulation from ARM guest to x86-32 host:
qemu-2.2.0: 29 seconds
qemu-2.6.
This seems to only affect fullscreen mode, so if that's the case, I
don't see it as resolved.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1274170
Title:
qemu window hides in the background on osx
On 03/08/2017 12:18 PM, Max Reitz wrote:
> In order to use error_setg() and similar functions, we need to include
> qapi/error.h.
>
> Signed-off-by: Max Reitz
> ---
> block/archipelago.c | 1 +
> 1 file changed, 1 insertion(+)
Reviewed-by: Eric Blake
Does this mean our automated buildbots are
On 08.03.2017 19:25, Eric Blake wrote:
> On 03/08/2017 12:18 PM, Max Reitz wrote:
>> In order to use error_setg() and similar functions, we need to include
>> qapi/error.h.
>>
>> Signed-off-by: Max Reitz
>> ---
>> block/archipelago.c | 1 +
>> 1 file changed, 1 insertion(+)
>
> Reviewed-by: Eric
On 03/08/2017 12:25 PM, Eric Blake wrote:
> On 03/08/2017 12:18 PM, Max Reitz wrote:
>> In order to use error_setg() and similar functions, we need to include
>> qapi/error.h.
>>
>> Signed-off-by: Max Reitz
>> ---
>> block/archipelago.c | 1 +
>> 1 file changed, 1 insertion(+)
>
> Reviewed-by: E
On 08.03.2017 19:28, Eric Blake wrote:
> On 03/08/2017 12:25 PM, Eric Blake wrote:
>> On 03/08/2017 12:18 PM, Max Reitz wrote:
>>> In order to use error_setg() and similar functions, we need to include
>>> qapi/error.h.
>>>
>>> Signed-off-by: Max Reitz
>>> ---
>>> block/archipelago.c | 1 +
>>> 1
On 03/08/2017 03:25 PM, Eric Blake wrote:
On 03/08/2017 12:18 PM, Max Reitz wrote:
In order to use error_setg() and similar functions, we need to include
qapi/error.h.
Signed-off-by: Max Reitz
---
block/archipelago.c | 1 +
1 file changed, 1 insertion(+)
Reviewed-by: Eric Blake
Reviewed-
1 - 100 of 177 matches
Mail list logo
