On 30/07/16 2:19 am, "Eric Blake" wrote:
>On 07/28/2016 01:07 AM, Prerna Saxena wrote:
>> From: Prerna Saxena
>>
>> This introduces the VHOST_USER_PROTOCOL_F_REPLY_ACK.
>>
>
>> +
>> +With this protocol extension negotiated, the sender (QEMU) can set the
>> +"need_reply" [Bit 3] flag to an
> -Original Message-
> From: virtio-...@lists.oasis-open.org [mailto:virtio-...@lists.oasis-open.org]
> On Behalf Of Michael S. Tsirkin
> Sent: Friday, July 29, 2016 1:34 PM
> To: Zeng, Xin
> Cc: Gonglei (Arei); qemu-devel@nongnu.org; virtio-...@lists.oasis-open.org;
> Ola Liljedahl; Keat
> -Original Message-
> From: Stefan Hajnoczi [mailto:stefa...@gmail.com]
> Sent: Friday, July 29, 2016 9:49 PM
> To: Gonglei (Arei)
> Cc: qemu-devel@nongnu.org; virtio-...@lists.oasis-open.org; Ola Liljedahl;
> Keating Brian; Michael S . Tsirkin; Zeng Xin; Hanweidong (Randy); Luonengjun;
>
On 07/28/2016 01:07 AM, Prerna Saxena wrote:
> From: Prerna Saxena
>
> This introduces the VHOST_USER_PROTOCOL_F_REPLY_ACK.
>
> +
> +With this protocol extension negotiated, the sender (QEMU) can set the
> +"need_reply" [Bit 3] flag to any command. This indicates that
> +the client MUST respond
On 07/29/2016 09:31 AM, Felipe Franciosi wrote:
> Heya,
>
> On 29 Jul 2016, at 13:47, Marc-André Lureau
> mailto:marcandre.lur...@gmail.com>> wrote:
>
> Hi
>
> On Thu, Jul 28, 2016 at 11:07 AM, Prerna Saxena
> mailto:saxenap@gmail.com>> wrote:
> From: Prerna Saxena
> mailto:prerna.sax...@
Hello,
On behalf of the QEMU Team, I'd like to announce the availability of the
second release candidate for the QEMU 2.7 release. This release is meant
for testing purposes and should not be used in a production environment.
http://wiki.qemu.org/download/qemu-2.7.0-rc1.tar.bz2
You can help imp
On 07/28/2016 02:51 PM, Michael S. Tsirkin wrote:
>> > If 1MB is too big, how about 512K, or 256K? 32K seems too small.
>> >
> It's only small because it makes you rescan the free list.
> So maybe you should do something else.
> I looked at it a bit. Instead of scanning the free list, how about
>
From: Prerna Saxena
The set_mem_table command currently does not seek a reply. Hence, there is
no easy way for a remote application to notify to QEMU when it finished
setting up memory, or if there were errors doing so.
As an example:
(1) Qemu sends a SET_MEM_TABLE to the backend (eg, a vhost-us
From: Prerna Saxena
This introduces the VHOST_USER_PROTOCOL_F_REPLY_ACK.
If negotiated, client applications should send a u64 payload in
response to any message that contains the "need_reply" bit set
on the message flags. Setting the payload to "zero" indicates the
command finished successfully.
From: Prerna Saxena
*** BLURB HERE ***
vhost-user: Extend protocol to receive replies on any command.
The current vhost-user protocol requires the client to send reply to only a
few commands. For the remaining commands, it is impossible for QEMU to know the
status of the requested operation -- i
Heya,
On 29 Jul 2016, at 13:47, Marc-André Lureau
mailto:marcandre.lur...@gmail.com>> wrote:
Hi
On Thu, Jul 28, 2016 at 11:07 AM, Prerna Saxena
mailto:saxenap@gmail.com>> wrote:
From: Prerna Saxena
mailto:prerna.sax...@nutanix.com>>
This introduces the VHOST_USER_PROTOCOL_F_REPLY_ACK.
I
On 26 July 2016 at 07:32, kwangwoo@sk.com wrote:
> NVDIMM stands for Non-Volatile DIMM which has DIMM form factor like PC-DIMM
> (Memory Module used in PC) and can be used like a memory, but the stored data
> is preserved on power failure. So it can be used as a memory, a storage, or
> backup
On 20 July 2016 at 01:49, Kwangwoo Lee wrote:
> Add hotplug memory feature on aarch64 virt platfom. This patch is
> required to emulate a DIMM type memory like NVDIMM.
>
> Signed-off-by: Kwangwoo Lee
> ---
> default-configs/aarch64-softmmu.mak | 1 +
> hw/arm/virt.c | 110
On 14 July 2016 at 01:03, Alistair Francis wrote:
> Signed-off-by: Alistair Francis
> ---
> V9:
> - Clarify the image loading options
> V8:
> - Improve documentation
> V6:
> - Fixup documentation
> V4:
> - Re-write to be more comprehensive
>
> docs/generic-loader.txt | 63
>
On 14 July 2016 at 01:03, Alistair Francis wrote:
> Add a new function load_image_targphys_as() that allows the caller
> to specify an AddressSpace to use when loading a targphys. The
> original load_image_targphys() function doesn't have any change in
> functionality.
>
> Signed-off-by: Alistair
On 14 July 2016 at 01:03, Alistair Francis wrote:
> Add a new function load_uimage_as() that allows the caller to
> specify an AddressSpace to use when loading the uImage. The
> original load_uimage() function doesn't have any change in
> functionality.
>
> Signed-off-by: Alistair Francis
> ---
>
On 14 July 2016 at 01:03, Alistair Francis wrote:
> Add a new function load_elf_as() that allows the caller to specify an
> AddressSpace to use when loading the ELF. The original load_elf()
> function doesn't have any change in functionality.
>
> Signed-off-by: Alistair Francis
> ---
> V8:
> - I
On 14 July 2016 at 01:03, Alistair Francis wrote:
> Prevously the specified MemoryRegion was ignored during the rom register
> reset. This patch uses the rom MemoryRegion is avaliable.
"if available"
>
> Signed-off-by: Alistair Francis
> ---
Reviewed-by: Peter Maydell
thanks
-- PMM
I'm running current master of QEMU using virgl and display backend
"gtk,gl=on". I get no guest mouse events unless I force CONFIG_GTK_GL
off or make the following patch. Key events work fine. I'm on ubuntu
16.04 with GTK 3.18 (ubuntu 15.10/GTK 3.16 also had the same issue).
I've had this problem fo
On Tue, 19 Jul 2016 15:32:43 +0800
Zhou Jie wrote:
> From: Chen Fan
>
> During aer err occurs and resume do following to
> protect device from being accessed.
> 1. Make config space read only.
> 2. Disable INTx/MSI Interrupt.
> 3. Do nothing for bar regions.
>
> Signed-off-by: Zhou Jie
> ---
On Tue, 19 Jul 2016 15:52:45 +0800
Zhou Jie wrote:
> From: Chen Fan
An empty commit log is unacceptable for all but the most trivial
patches.
There's also no sign-off on this patch.
I also don't know why we need this since you previously found that for
QEMU, ordering of error versus resume no
LINK sparc-bsd-user/qemu-sparc
bsd-user/main.o: In function `cpu_loop':
/home/sbruno/bsd/qemu/bsd-user/main.c:515: undefined reference to
`cpu_sparc_exec'
c++: error: linker command failed with exit code 1 (use -v to see invocation)
gmake[1]: *** [Makefile:197: qemu-sparc] Error 1
gmake: *** [M
On 14 July 2016 at 01:03, Alistair Francis wrote:
> If the caller didn't specify an architecture for the ELF machine
> the load_elf() function will auto detect it based on the ELF file.
>
> Signed-off-by: Alistair Francis
> ---
> V9:
> - Update documentation
> V8:
> - Move into load_elf64/load_
On 14 July 2016 at 01:03, Alistair Francis wrote:
> When loading ROMs allow the caller to specify an AddressSpace to use for
> the load.
>
> Signed-off-by: Alistair Francis
> ---
> V9:
> - Fixup the ROM ordering
> - Don't allow address space and memory region to be specified
> V8:
> - Introduc
Signed-off-by: Michael Rolnik
---
target-avr/Makefile.objs|2 +-
target-avr/translate-inst.c | 2622 +++
target-avr/translate.c |1 -
target-avr/translate.h |1 +
4 files changed, 2624 insertions(+), 2 deletions(-)
create mode 100
Signed-off-by: Michael Rolnik
---
target-avr/cpugen/CMakeLists.txt | 38 +++
target-avr/cpugen/README.md| 17 ++
target-avr/cpugen/cpu/avr.yaml | 214 ++
target-avr/cpugen/src/CMakeLists.txt | 63
target-avr/cpugen/src/cpugen.cpp
Signed-off-by: Michael Rolnik
---
target-avr/translate-inst.h | 805
1 file changed, 805 insertions(+)
create mode 100644 target-avr/translate-inst.h
diff --git a/target-avr/translate-inst.h b/target-avr/translate-inst.h
new file mode 100644
index 00
Signed-off-by: Michael Rolnik
---
target-avr/cpu.h | 13 ++-
target-avr/helper.c| 288 ++---
target-avr/helper.h| 8 +-
target-avr/translate.c | 9 ++
4 files changed, 300 insertions(+), 18 deletions(-)
diff --git a/target-avr/cpu.h
Signed-off-by: Michael Rolnik
---
target-avr/helper.c | 59 -
1 file changed, 58 insertions(+), 1 deletion(-)
diff --git a/target-avr/helper.c b/target-avr/helper.c
index 3984fc8..1e5d97d 100644
--- a/target-avr/helper.c
+++ b/target-avr/helper
Signed-off-by: Michael Rolnik
---
MAINTAINERS | 6 +++
hw/avr/Makefile.objs | 21 +
hw/avr/sample.c | 117 +++
3 files changed, 144 insertions(+)
create mode 100644 hw/avr/Makefile.objs
create mode 100644 hw/avr/sample.c
1. basic CPU structure
2. registers
3. no instructions
4. saving sreg, rampD, rampX, rampY, rampD, eind in HW representation
Signed-off-by: Michael Rolnik
---
arch_init.c | 2 +
configure | 5 +
default-configs/avr-softmmu.mak | 21 +
Signed-off-by: Michael Rolnik
---
target-avr/cpu.c | 319 +--
target-avr/cpu.h | 52 -
target-avr/machine.c | 28 ++---
3 files changed, 373 insertions(+), 26 deletions(-)
diff --git a/target-avr/cpu.c b/target-avr/cpu.c
index c5e
This series of patches adds 8bit AVR cores to QEMU.
All instruction, except BREAK/DES/SPM/SPMX, are implemented. Not fully tested
yet.
However I was able to execute simple code with functions. e.g fibonacci
calculation.
This series of patches include a non real, sample board.
No fuses support yet
On 29 July 2016 at 07:54, Andrew Jones wrote:
> OK, so this property will be exposed to all ARM cpu types, and if a user
> turns it on, then it will stay on for all types, except when using KVM
> with an aarch64 cpu type, and KVM doesn't support it. This could mislead
> users to believe they'll ge
On 29 July 2016 at 16:08, Wei Huang wrote:
>
>
> On 07/29/2016 02:57 AM, Peter Maydell wrote:
>> On 28 July 2016 at 17:38, Wei Huang wrote:
>>> This patch adds a pmu=[on/off] option to enable/disable vpmu support
>>> in guest vm. There are several reasons to justify this option. First
>>> vpmu ca
On Fri, Jul 29, 2016 at 12:17:43PM +0100, Daniel P. Berrange wrote:
> The virtio-console.c file handles both serial consoles
> and interactive consoles, since they're backed by the
> same device model.
>
> Since serial devices are expected to be reliable and
> need to notify the guest when the bac
On Thu, 28 Jul 2016 23:47:58 +
"Tian, Kevin" wrote:
> > From: Alex Williamson [mailto:alex.william...@redhat.com]
> > Sent: Thursday, July 28, 2016 11:42 PM
> >
> > On Thu, 28 Jul 2016 10:15:24 +
> > "Tian, Kevin" wrote:
> >
> > > Hi, Alex,
> > >
> > > Along with recent enhancement o
The about dialog in QEMU on Mac OS X is very plain and unhelpful. This patch
makes the about dialog look a lot better and have some descriptive information
on what version of QEMU the user is running.
Signed-off-by: John Arbuckle
---
version 3 changes:
Removed buffer related code
version 2 chang
On 07/29/2016 02:57 AM, Peter Maydell wrote:
> On 28 July 2016 at 17:38, Wei Huang wrote:
>> This patch adds a pmu=[on/off] option to enable/disable vpmu support
>> in guest vm. There are several reasons to justify this option. First
>> vpmu can be problematic for cross-migration between differe
On 07/29/2016 01:54 AM, Andrew Jones wrote:
> On Thu, Jul 28, 2016 at 11:38:16AM -0500, Wei Huang wrote:
>> This patch adds a pmu=[on/off] option to enable/disable vpmu support
>> in guest vm. There are several reasons to justify this option. First
>> vpmu can be problematic for cross-migration b
Ok, now it makes more sense. You are using the socket chardev in TCP
outgoing client mode, which used to be blocking by default. In 2.6 this
switched to match TCP server mode, in wich the incoming client was
always in non-blocking mode.
IOW, this arm code was already broken in 2.5 just depending
** Summary changed:
- "-serial unix:" option of qemu-system-* is broken in qemu 2.6.0
+ "-serial unix:" option of qemu-system-arm is broken in qemu 2.6.0
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs
I wrote small code which reproduces this issue.
https://bitbucket.org/redcap97/puts-hello-x8-armv7-kernel/downloads
/puts-HELLO-x8
Above binary outputs "HELLO!" 8 times to UART.
# Please execute in terminal
socat unix-listen:a.sock stdout | tee actual
# Please execute in another ter
> Looking at the code in 2.5.0, the qemu_chr_fe_write method would see
EAGAIN too, because the tcp_chr_accept() method would always set the
newly connected client to non-blocking mode. So thre's no obvious change
in behaviour between 2.5 and 2.6 wrt to blocking sockets.
It looks like tcp_chr_accep
Sorry, this issue only occur in qemu-system-arm (vexpress-a9).
In hw/char/pl011.c, qemu_chr_fe_write function is called directly and EAGAIN
isn't handled.
http://git.qemu.org/?p=qemu.git;a=blob;f=hw/char/pl011.c;h=210c87b4c2bd000d80c359ca5c05d43c64210677;hb=bfc766d38e1fae5767d43845c15c79ac8fa6d6a
Since 7f0317cfc8da6 we have API to specify the ID of block jobs and we
also guarantee that they are well-formed and unique.
This patch adds tests to check some common scenarios.
Signed-off-by: Alberto Garcia
---
tests/Makefile.include | 2 +
tests/test-blockjob.c | 147 ++
On 29 July 2016 at 15:13, Auger Eric wrote:
> Hi Peter,
> On 29/07/2016 15:35, Peter Maydell wrote:
>> On 6 July 2016 at 10:46, Eric Auger wrote:
>>> +/**
>>> + *
>>> + * We currently do not use kvm_arm_register_device to provide
>>> + * the kernel with the vITS control frame base address since t
On 19 July 2016 at 20:12, Dr. David Alan Gilbert wrote:
> * Aaron Lindsay (alind...@codeaurora.org) wrote:
>> This avoids a segfault like the following for at least some 4.8 versions
>> of gcc when configured with --static if avx2 instructions are also
>> enabled:
>>
>> Program received sign
Hi Peter,
On 29/07/2016 15:35, Peter Maydell wrote:
> On 6 July 2016 at 10:46, Eric Auger wrote:
>> +/**
>> + *
>> + * We currently do not use kvm_arm_register_device to provide
>> + * the kernel with the vITS control frame base address since the
>> + * KVM_DEV_ARM_VGIC_CTRL_INIT init MUST be call
On Wed, Jul 27, 2016 at 08:08:20PM +0300, Denis V. Lunev wrote:
> From: Klim Kireev
>
> Before this patch incorrect image could be created via qemu-img
> (Example: qemu-img create -f parallels -o size=4096T hack.img),
> incorrect images cannot be used due to overflow in main image structure.
>
>
commit f6e98444 (apic: Use apic_id as apic's migration instance_id)
breaks migration when in kernel irqchip is used for 2.6 and older
machine types.
It applies compat property only for userspace 'apic' type
instead of applying it to all apic types inherited from
'apic-common' type as it was suppos
On 13 June 2016 at 17:27, wrote:
> From: KONRAD Frederic
>
> Hi,
>
> This is a first draft of the clock framework API it contains:
>
> * The first 5 patches which introduce the framework.
> * The 6th patch which introduces a fixed-clock model.
> * The rest which gives an example how to mod
On 26 July 2016 at 22:05, Sean Bruno wrote:
> Update the build flags appropriately for FreeBSD and add the
> correct LD_EMULATION type for the FreeBSD build case.
>
> Fixes FreeBSD build error:
> ld: unrecognised emulation mode: elf_i386
> Supported emulations: elf_x86_64_fbsd elf_
On 13 June 2016 at 17:27, wrote:
> From: KONRAD Frederic
>
> This adds the pll to the zynqmp_crf and the dp_video clock output.
>
> Signed-off-by: KONRAD Frederic
> ---
> hw/misc/xilinx_zynqmp_crf.c | 440
>
> 1 file changed, 440 insertions(+)
>
>
On Wed, Jul 27, 2016 at 06:08:23PM +0800, Gonglei wrote:
> +The first driver-read-only field, \field{version} specifies the virtio
> crypto??s
> +version, which is reserved for back-compatibility in future.It??s currently
Here...
> +Step2: Execute the detail encryption operation:
> +\begin{enume
On 13 June 2016 at 17:27, wrote:
> From: KONRAD Frederic
>
> This seems to be due to a difference between the AF_EX32 define.
>
> Signed-off-by: KONRAD Frederic
> ---
> hw/misc/xilinx_zynqmp_crf.c | 354
> ++--
> 1 file changed, 177 insertions(+), 177 d
On 13 June 2016 at 17:27, wrote:
> From: KONRAD Frederic
>
> This adds the qemu-clock documentation.
>
> Signed-off-by: KONRAD Frederic
> ---
> docs/clock.txt | 112
> +
> 1 file changed, 112 insertions(+)
> create mode 100644 docs/cloc
On 13 June 2016 at 17:27, wrote:
> From: KONRAD Frederic
>
> This introduces the clock binding and the update part.
> When the qemu_clk_rate_update(qemu_clk, int) function is called:
> * The clock callback is called on the qemu_clk so it can change the rate.
> * The qemu_clk_rate_update func
On 07/28/2016 11:03 PM, Eric Blake wrote:
> On 07/28/2016 09:29 AM, Halil Pasic wrote:
>
>>> You mean va_start, not start_va. And actually, C11 is clear that errno
>>> is unspecified after library functions (but not macros) that don't
>>> explicitly state otherwise. Since va_start() is a macro
On 27/07/16 16:56, Juergen Gross wrote:
> I can reproduce a problem in qemu with Xen just by adding and removing a
> USB bus. The bus is added via usb_bus_new() in hw/usb/xen-usb.c and
> removed later via usb_bus_release().
>
> Nothing bad happens until I close an active VNC viewer connected to th
On 6 July 2016 at 10:46, Eric Auger wrote:
> +/**
> + *
> + * We currently do not use kvm_arm_register_device to provide
> + * the kernel with the vITS control frame base address since the
> + * KVM_DEV_ARM_VGIC_CTRL_INIT init MUST be called after the
> + * KVM_ARM_SET_DEVICE_ADDR and the kvm_arm_
On 20 July 2016 at 20:36, Paolo Bonzini wrote:
> The cc-option macro runs $(CC) in -S mode (generate assembly) to avoid a
> pointless run of the assembler. However, this does not work when you want
> to detect support for cc->as option passthrough. clang ignores -Wa unless
> -c is provided, and
David Gibson wrote on 07/29/2016 12:40:15
AM:
> From: David Gibson
> To: alar...@ddci.com
> Cc: qemu-devel@nongnu.org, qemu-...@nongnu.org, ag...@suse.de
> Date: 07/29/2016 12:38 AM
> Subject: Re: target-ppc: SPR_BOOKE_ESR not set on FP exceptions
>
> On Thu, Jul 28, 2016 at 06:32:27PM -0500,
cking branch 'remotes/ehabkost/tags/x86-pull-request' into
> staging (2016-07-27 18:18:21 +0100)
>
> are available in the git repository at:
>
> git://github.com/lalrae/qemu.git tags/mips-20160729
>
> for you to fetch changes up to 701074a6fc7470d0ed54e4a4bcd4d
Hi
On Thu, Jul 28, 2016 at 11:07 AM, Prerna Saxena wrote:
> From: Prerna Saxena
>
> This introduces the VHOST_USER_PROTOCOL_F_REPLY_ACK.
>
> If negotiated, client applications should send a u64 payload in
> response to any message that contains the "need_reply" bit set
> on the message flags. Se
On 07/29/2016 02:30 PM, Benjamin Herrenschmidt wrote:
DEF_HELPER_3(lmw, void, env, tl, i32)
-DEF_HELPER_3(stmw, void, env, tl, i32)
+DEF_HELPER_FLAGS_3(stmw, TCG_CALL_NO_WG, void, env, tl, i32)
DEF_HELPER_4(lsw, void, env, tl, i32, i32)
DEF_HELPER_5(lswx, void, env, tl, i32, i32, i32)
-DEF_HEL
On 07/29/2016 10:26 AM, David Gibson wrote:
Btw, your mailer seems to have screwed up and sent this as html only.
"Sent from my phone" should have been the disclaimer. ;-)
r~
On 07/29/2016 12:26 PM, Benjamin Herrenschmidt wrote:
I notice that sadly, all of the vector ops are helper with full
clobbers, because I assume, the "avr" is passed as pointer due to the
lack of an int128 type in TCG correct ?
Yes. Although x86 doesn't declare the vector registers as tcg regi
On 07/29/2016 12:26 PM, Benjamin Herrenschmidt wrote:
So I can't do something like set TCG_CALL_NO_RWG (nor TCG_CALL_NO_WG)
on something like dcbz because it can take an exception, correct ?
You can't set NO_RWG, but you can say NO_WG. It "reads" the registers via the
exception (and it certai
Patch at https://lists.gnu.org/archive/html/qemu-
devel/2016-07/msg06708.html
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1599214
Title:
virtlogd: qemu 2.6.0 doesn't log boot message
Status in Q
ble in the git repository at:
>
> git://github.com/dgibson/qemu.git tags/ppc-for-2.7-20160729
>
> for you to fetch changes up to 059ce0f00af0124740bcb9991d160f93c92ae174:
>
> tests: add drive_del-test to ppc/ppc64 (2016-07-29 14:14:15 +1000)
>
> ---
On 29 July 2016 at 04:14, Michael S. Tsirkin wrote:
> The following changes since commit 2d2e632ad00d11867c6c5625605b1fbc022dd62f:
>
> Update version for v2.7.0-rc0 release (2016-07-22 15:32:42 +0100)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/virt/kvm/mst/qem
The virtio-console.c file handles both serial consoles
and interactive consoles, since they're backed by the
same device model.
Since serial devices are expected to be reliable and
need to notify the guest when the backend is opened
or closed, the virtio-console.c file wires up support
for chardev
When unplugging a device in the Xen pvusb backend drain the submit
queue before deallocation of the control structures. Otherwise there
will be bogus memory accesses when I/O contracts are finished.
Correlated to this issue is the handling of cancel requests: a packet
cancelled will still lead to
When a Xenstore watch fires indicating a backend has to be removed
don't remove all backends for that domain with the specified device
index, but just the one which has the correct type.
The easiest way to achieve this is to use the already determined
xendev as parameter for xen_be_del_xendev() in
When testing qemu based pvusb backend two bugs have been discovered:
- detaching of a usb controller leads to memory clobbering in qemu
- detaching of a usb device with active I/O requests could result in
crash of qemu
Juergen Gross (2):
xen: when removing a backend don't remove many of them
The returned value of cpu_get_clock() is plused with the offset,
so it is the time elapsed in virtual machine when vm is active.
Cc: Paolo Bonzini
Cc Peter Crosthwaite
Cc: Richard Henderson
Signed-off-by: Cao jin
---
cpus.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --g
Cc: Paolo Bonzini
Cc: Peter Maydell
Cc Peter Crosthwaite
Cc: Richard Henderson
Cao jin (3):
timer: update comments
cpus: rename local variable to meaningful one
cpus: update comments
cpus.c | 13 +++--
include/qemu/timer.h | 19 ++-
2 files change
The function actually returns monotonic time value in nanosecond,
the "ticks" is not suitable.
Cc: Paolo Bonzini
Cc Peter Crosthwaite
Cc: Richard Henderson
Signed-off-by: Cao jin
---
cpus.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/cpus.c b/cpus.c
index d4af
The comments is outdated. The patch has following changes:
1. tense correction.
2. all clock time value is returned in nanoseconds, so, they are same in
precision.
3. virtual clock doesn't use cpu cycles.
Cc: Paolo Bonzini
Cc: Peter Maydell
Signed-off-by: Cao jin
---
include/qemu/timer.h | 19
On 28 July 2016 at 23:50, John Snow wrote:
> The following changes since commit 21a21b853a1bb606358af61e738abfb9aecbd720:
>
> Merge remote-tracking branch 'remotes/ehabkost/tags/x86-pull-request' into
> staging (2016-07-27 18:18:21 +0100)
>
> are available in the git repository at:
>
> https:
* Denis V. Lunev (d...@openvz.org) wrote:
> From: Evgeny Yakovlev
>
> mmap man page:
> "On success, mmap() returns a pointer to the mapped area. On error, the
> value MAP_FAILED (that is, (void *) -1) is returned, and errno is set
> to indicate the cause of the error."
>
> The check in postcop
On (Fri) 29 Jul 2016 [12:48:25], Denis V. Lunev wrote:
> From: Evgeny Yakovlev
>
> mmap man page:
> "On success, mmap() returns a pointer to the mapped area. On error, the
> value MAP_FAILED (that is, (void *) -1) is returned, and errno is set
> to indicate the cause of the error."
>
> The che
Fam,
On 07/29/16 12:22, Fam Zheng wrote:
> At system_reset, there is no point in retrying the queued request,
> because the driver that issued the request won't be around any more.
>
> Analyzed-by: Laszlo Ersek
> Reported-by: Laszlo Ersek
> Signed-off-by: Fam Zheng
> ---
> hw/block/virtio-blk
Hi,
Does anyone know the reason for, VM resizing time to increase faster if you
continuously increase CPU or DISK resources by +1 (e.g. 1-2, 2-3, 3-4, 4-5).
Whereas, when you increase from 1 to any other (e.g. 1-2, 1-2, 1,3, 1-4, 1-5)
it takes less time in comparison. Can anyone give an explana
At system_reset, there is no point in retrying the queued request,
because the driver that issued the request won't be around any more.
Analyzed-by: Laszlo Ersek
Reported-by: Laszlo Ersek
Signed-off-by: Fam Zheng
---
hw/block/virtio-blk.c | 6 ++
1 file changed, 6 insertions(+)
diff --git
From: Evgeny Yakovlev
mmap man page:
"On success, mmap() returns a pointer to the mapped area. On error, the
value MAP_FAILED (that is, (void *) -1) is returned, and errno is set
to indicate the cause of the error."
The check in postcopy_get_tmp_page is definitely wrong and should be
fixed.
S
On Fri, Jul 29, 2016 at 10:15:46AM +0800, Cao jin wrote:
> Follow CODING_STYLE
>
> Cc: Daniel P. Berrange
> Cc: Gerd Hoffmann
> Cc: Paolo Bonzini
> Cc: Eric Blake
> Signed-off-by: Cao jin
> ---
> util/qemu-sockets.c | 12 +++-
> 1 file changed, 7 insertions(+), 5 deletions(-)
>
> v2
While implementing TLB invalidation feature we forgot to modify
part of code responsible for updating EntryHi during TLB exception.
Consequently EntryHi.EHINV is unexpectedly cleared on the exception.
Signed-off-by: Leon Alrae
---
target-mips/helper.c | 1 +
1 file changed, 1 insertion(+)
diff
0100)
are available in the git repository at:
git://github.com/lalrae/qemu.git tags/mips-20160729
for you to fetch changes up to 701074a6fc7470d0ed54e4a4bcd4d491ad8da22e:
target-mips: fix EntryHi.EHINV being cleared on TLB exception (2016-07-28
11:2
From: Paul Burton
The print routine provided as part of the in-built bootloader had a bug
in that it attempted to use a jump instruction as part of a loop, but
the target has its upper bits zeroed leading to control flow
transferring to 0xb814 rather than the intended 0xbfc00814. Fix this
by
On Fri, 2016-07-29 at 06:19 +0530, Richard Henderson wrote:
> (1) The helper, since it writes to registers controlled by tcg, must be
> described to clobber all registers. Which will noticeably increase memory
> traffic to ENV. For instance, you won't be able to hold the guest register
> holdi
Hi
On Fri, Jul 29, 2016 at 2:16 AM, Eric Blake wrote:
> On 07/28/2016 08:38 AM, marcandre.lur...@redhat.com wrote:
>> From: Marc-André Lureau
>>
>> Allows to specify a destroy function for the test data.
>
> "Allows to" is not idiomatic English. Alternatives that sound better are
> "Allows $who
Also while at it, group the #include statements in translate.c
Signed-off-by: Benjamin Herrenschmidt
---
v3. Stupid typo I corrected locally but din't commit...
v2. Rebase on top of ppc-for-2.8
Use git renames
target-ppc/translate.c | 40 +++---
Also while at it, group the #include statements in translate.c
Signed-off-by: Benjamin Herrenschmidt
---
v2. Rebase on top of ppc-for-2.8
Use git renames
target-ppc/translate.c | 40 +++---
.../translate/{dfp-impl.c => dfp-impl.inc.c} | 0
Laszlo Ersek writes:
> On 07/29/16 09:29, Markus Armbruster wrote:
>> Missed when commit 5712db6 split off "fw_cfg_io" and "fw_cfg_mem".
>>
>> Signed-off-by: Markus Armbruster
>> ---
>> hw/nvram/fw_cfg.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/hw/nvram/fw_cfg.c b/hw/nvram/
On 07/29/16 09:29, Markus Armbruster wrote:
> Missed when commit 5712db6 split off "fw_cfg_io" and "fw_cfg_mem".
>
> Signed-off-by: Markus Armbruster
> ---
> hw/nvram/fw_cfg.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/hw/nvram/fw_cfg.c b/hw/nvram/fw_cfg.c
> index 2873030..0ccab2d
On 28 July 2016 at 17:38, Wei Huang wrote:
> This patch adds a pmu=[on/off] option to enable/disable vpmu support
> in guest vm. There are several reasons to justify this option. First
> vpmu can be problematic for cross-migration between different SoC as
> perf counters is architecture-dependent.
On Friday, July 29, 2016 1:34 PM Michael S. Tsirkin Wrote:
> -Original Message-
> From: Michael S. Tsirkin [mailto:m...@redhat.com]
> Sent: Friday, July 29, 2016 1:34 PM
> To: Zeng, Xin
> Cc: Gonglei (Arei); qemu-devel@nongnu.org; virtio-dev@lists.oasis-
> open.org; Ola Liljedahl; Keating,
Hi
On Fri, Jul 29, 2016 at 10:31 AM, Igor Mammedov wrote:
> On Thu, 28 Jul 2016 17:43:37 +0400
> Marc-André Lureau wrote:
>
>> Hi
>>
>> On Thu, Jul 28, 2016 at 3:29 PM, Igor Mammedov wrote:
>> > On Thu, 28 Jul 2016 15:13:57 +0400
>> > marcandre.lur...@redhat.com wrote:
>> >
>> >> From: Marc-And
1 - 100 of 106 matches
Mail list logo
