Applied all to -trivial. Thank you!
/mjt
[dropping debian bugreport]
13.08.2014 10:05, Michael Tokarev wrote:
> [This is http://bugs.debian.org/757927 -- trim stopped working in qemu 2.1]
>
> 12.08.2014 18:46, Michael Tokarev wrote:
>> 12.08.2014 17:35, Roman Mamedov wrote:
>>> Package: qemu-kvm
>>> Version: 2.1+dfsg-2~bpo70+2
>>> Sever
13.08.2014 10:16, Roman Mamedov wrote:
> Thanks for working on this! Sorry for not being able to test an updated
> version sooner.
You're welcome. I learned something too ;)
[]
> I was only successful in using this with the virtual IDE interface disks on
> Qemu/KVM 2.0, the virtio mode does not
11.08.2014 12:10, arei.gong...@huawei.com wrote:
> From: Gonglei
>
> Gonglei (2):
> pci-host: update obsolete reference about piix_pci.c
> pci-host: update uncorresponding description
Applied both to -trivial, thank you!
/mjt
13.08.2014 07:20, Liming Wang wrote:
> Change host to port.
A good one. Applied to -trivial, thank you!
/mjt
Applied to -trivial, thank you!
/mjt
09.08.2014 18:05, Jan Kiszka wrote:
> From: Jan Kiszka
>
> IA-32 SDM, Figure 10-14: Bits 27:0 are reserved as 1.
>
> Fixes Jailhouse hypervisor start with in-kernel irqchips off.
Applied to -trivial, thank you!
Are the other similar cases in there okay?
Say, 0x0d or 0x02 which also uses shifts
The spec says (and real HW confirms this) that, if the bus master bit
is 0, the device will not generate any PCI accesses. MSI and MSI-X
messages fall among these, so we should use the corresponding address
space to deliver them. This will prevent delivery if bus master support
is disabled.
Signed
On 2014-08-01 08:22, Danzer, Uwe wrote:
> Hi there,
>
> I'm implementing an emulated PCIe Memory class device, but can't get MSI-X
> interrupt emulation working.
>
> So far, the card appears in the guest system and the driver for the card
> recognises it and the emulation of 1MB of accessible r
[This is http://bugs.debian.org/757927 -- trim stopped working in qemu 2.1]
12.08.2014 18:46, Michael Tokarev wrote:
> 12.08.2014 17:35, Roman Mamedov wrote:
>> Package: qemu-kvm
>> Version: 2.1+dfsg-2~bpo70+2
>> Severity: normal
>>
>> Hello,
>>
>> I was able to successfully use the passthrough TR
On 08/13/2014 03:00 PM, Gonglei (Arei) wrote:
> I noticed that QMP's "device_add usb-ehci,id=i2,bus=pci.0" fails on PCI
> hotplug. The same for pci-ohci and this is because their initfn() do
> "dc->hotpluggable = false". So I removed those and now I can hotplug
>> USB
> hosts but
On Tue, Aug 12, 2014 at 05:25:29PM +1000, Alexey Kardashevskiy wrote:
> On 08/12/2014 11:45 AM, David Gibson wrote:
> > On Thu, Jul 31, 2014 at 07:34:10PM +1000, Alexey Kardashevskiy
> wrote:
[snip]
> > The function of this is kind of unclear. I'm assuming this is
> > filtering the supported page
On Tue, Aug 12, 2014 at 08:54:34AM +0200, Eric Auger wrote:
> On 08/12/2014 04:41 AM, David Gibson wrote:
> > On Sat, Aug 09, 2014 at 03:25:44PM +0100, Eric Auger wrote:
> >> vfio_get_device now takes a VFIODevice as argument. The function is split
> >> into 4 functional parts: dev_info query, devi
On Tue, Aug 12, 2014 at 05:16:44PM +1000, Alexey Kardashevskiy wrote:
> On 08/12/2014 11:20 AM, David Gibson wrote:
> > On Thu, Jul 31, 2014 at 07:34:09PM +1000, Alexey Kardashevskiy wrote:
> >> Signed-off-by: Alexey Kardashevskiy
> >
> > It would be nice for your commit message to state exactly
> >>> I noticed that QMP's "device_add usb-ehci,id=i2,bus=pci.0" fails on PCI
> >>> hotplug. The same for pci-ohci and this is because their initfn() do
> >>> "dc->hotpluggable = false". So I removed those and now I can hotplug
> USB
> >>> hosts but none of them is able to actually work:
> >>>
>
On 08/12/2014 04:05 PM, Alexey Kardashevskiy wrote:
> On 08/11/2014 03:59 PM, Gonglei (Arei) wrote:
>> Hi,
>>
>>> Subject: [Qemu-devel] USB PCI host bus adapter hot plug
>>>
>>> Hi!
>>>
>>> I noticed that QMP's "device_add usb-ehci,id=i2,bus=pci.0" fails on PCI
>>> hotplug. The same for pci-ohci an
This patch makes the fault injection functionality of blkdebug
callable from QMP. Motivation of this change is for testing and
debugging distributed systems. Ordinal distributed systems must handle
hardware faults because of its reason for existence, but testing
whether the systems can hanle such f
> Subject: [Qemu-devel] [PATCH] qemu-options.hx: fix a typo of chardev
>
> Change host to port.
>
> Signed-off-by: Liming Wang
> ---
> qemu-options.hx | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
Reviewed-by: Gonglei
Cc'ing qemu-trivial@
Best regards,
-Gonglei
> diff --git a/
Change host to port.
Signed-off-by: Liming Wang
---
qemu-options.hx | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/qemu-options.hx b/qemu-options.hx
index 1549625..ac9e985 100644
--- a/qemu-options.hx
+++ b/qemu-options.hx
@@ -1926,7 +1926,7 @@ ETEXI
DEF("chardev", HAS_AR
I'm so glad to see my patches also work in your environment!!
That's really exciting.
I'm also wondering what will happen if integrating with irqfd.
BTW, would share your performance number?
Best Regards,
潘穎軒 Yingshiuan Pan
2014-08-13 10:23 GMT+08:00 Li Liu :
>
>
> On 2014/8/12 23:47, Nik
On 2014/8/12 23:47, Nikolay Nikolaev wrote:
> Hello,
>
>
> On Tue, Aug 12, 2014 at 5:41 AM, Li Liu wrote:
>>
>> Hi all,
>>
>> Is anyone there can tell the current status of vhost-net on kvm-arm?
>>
>> Half a year has passed from Isa Ansharullah asked this question:
>> http://www.spinics.net/li
On 2014/8/12 15:29, Eric Auger wrote:
> On 08/12/2014 04:41 AM, Li Liu wrote:
>> Hi all,
>>
>> Is anyone there can tell the current status of vhost-net on kvm-arm?
>>
>> Half a year has passed from Isa Ansharullah asked this question:
>> http://www.spinics.net/lists/kvm-arm/msg08152.html
>>
>> I
On Tue, 08/12 14:44, John Snow wrote:
> Currently, if the block device backing the IDE drive is resized,
> the information about the device as cached inside of the IDEState
> structure is not updated, thus when a guest OS re-queries the drive,
> it is unable to see the expanded size.
>
> This patc
On Tue, 08/12 16:12, Daniel Henrique Barboza wrote:
> The curl hardcoded timeout (5 seconds) sometimes is not long
> enough depending on the remote server configuration and network
> traffic. The user should be able to set how much long he is
> willing to wait for the connection.
>
> Adding a new
On Tue, 08/12 12:22, Xingbo Wu wrote:
> On Tue, Aug 12, 2014 at 11:30 AM, Eric Blake wrote:
>
> > On 08/12/2014 08:14 AM, 吴兴博 wrote:
> > >>> However FVD seems to have been ignored by community.
> > >>
> > >> Care to give a pointer to a URL describing the FVD format?
> > >>
> > >> http://lists.non
As of qemu-2.1, spapr/pseries, has a set of versioned machine classes to
represent the machine type as it appeared to the guest in different qemu
versions. This allows for safe migration of guests between current and
future qemu versions.
In PC, however, the default plain "pc" machine type is jus
after the recent ui rework it didn't show a gfx window if no emulated
graphics card was attached. This prevented input grab from working for
the vfio gpu passthrough use case.
Hack around this by always creating at least one gfx tab.
---
I'm not quite sure how much of a hack this is, but it at le
On 08/13/2014 01:28 AM, Alexander Graf wrote:
>
> On 12.08.14 17:10, Alexey Kardashevskiy wrote:
>> On 08/12/2014 07:37 PM, Alexander Graf wrote:
>>> On 12.08.14 02:03, Alexey Kardashevskiy wrote:
On 08/12/2014 03:30 AM, Alexander Graf wrote:
> On 11.08.14 17:01, Alexey Kardashevskiy wrot
>>No, you should lay 'kvm: -device virtio-serial,id=spice,bus=pci.0' before
>>"-readconfig /usr/share/qemu-server/pve-q35.cfg",which can assure
>>the bus pci.0 has been created.
Oh, you are right, I didn't notice that pci bridge was defined after this
device.
Sorry to disturb the mailing list ab
On 08/12/2014 11:43 PM, Laszlo Ersek wrote:
> On 08/03/14 17:28, Chen Gang wrote:
>> In dump_init(), when failure occurs, need notice about 'fd' and memory
>> mapping. So call dump_cleanup() for it (need let all initializations at
>> front).
>>
>> Also simplify dump_cleanup(): remove redundant 'ret
Pinging this as I'm running into the same issue, Win7 seems to be fine
as a guest, just getting this with XP (SP3).
I'm 99% certain that 1.5.0 was still fine. I looked at the commits
between that and 1.5.2 but did not really see anything obvious that
could cause it.
--
You received this bug noti
On Tue, Aug 12, 2014 at 03:23:38PM -0400, Xingbo Wu wrote:
> would be very space efficient for distribution :).
> Would you consider replace xz with lz4? it has faster decompression speed
> (~500MB/s)[1] and client-side decompression would be made painless.
No. The main benefit of xz is it has a
Implement Short Floating-Point Store Instructions as described
in the chapter 13.5.2 of UltraSPARC-IIi User's Manual.
Particularly this instructions are used by NetBSD 4.0.1+ /sparc64
Signed-off-by: Artyom Tarasenko
Tested-by: Mark Cave-Ayland
---
With this patch applied on top of cmd646 patche
On Tue, Aug 12, 2014 at 09:12:00PM +0200, Paolo Bonzini wrote:
> Il 12/08/2014 20:55, Eduardo Habkost ha scritto:
> > This makes the CPUID data change under the guest's feet during
> > live-migration.
> >
> > Adding compat code to ensure older machine-types keep the old behavior
> > is necessary,
On Tuesday, August 12, 2014, Richard Henderson wrote:
> On 08/08/2014 10:48 AM, Artyom Tarasenko wrote:
>> Implement Short Floating-Point Store Instructions as described
>> in the chapter 13.5.2 of UltraSPARC-IIi User's Manual.
>>
>> Particularly this instructions are used by NetBSD 4.0.1+ /sparc6
On Tue, Aug 12, 2014 at 2:52 PM, Richard W.M. Jones
wrote:
> On Tue, Aug 12, 2014 at 07:46:30PM +0100, Daniel P. Berrange wrote:
> > Taking the compression feature - arguably the biggest benefit of that
> > is when you distribute disk images. eg if someone provides a root disk
> > image on a web
The curl hardcoded timeout (5 seconds) sometimes is not long
enough depending on the remote server configuration and network
traffic. The user should be able to set how much long he is
willing to wait for the connection.
Adding a new option to set this timeout gives the user this
flexibility. The
Il 12/08/2014 20:55, Eduardo Habkost ha scritto:
> This makes the CPUID data change under the guest's feet during
> live-migration.
>
> Adding compat code to ensure older machine-types keep the old behavior
> is necessary, but in this specific case it is mostly harmless because
> 0x0 is documented
Il 12/08/2014 10:12, Ming Lei ha scritto:
>> > The below patch is basically the minimal change to bypass coroutines. Of
>> > course
>> > the block.c part is not acceptable as is (the change to
>> > refresh_total_sectors
>> > is broken, the others are just ugly), but it is a start. Please run it
The argument to the mlockall system call is not necessarily the same on
all platforms and thus may require translation prior to passing to the
host.
For example, PowerPC 64 bit platforms define values for MCL_CURRENT
(0x2000) and MCL_FUTURE (0x4000) which are different from Intel platforms
(0x1 an
Although not technically not required by POSIX, the writev system call will
typically write out its buffers individually. That is, if the first buffer
is written successfully, but the second buffer pointer is invalid, then
the first chuck will be written and its size is returned.
Signed-off-by: T
On Wed, Jun 04, 2014 at 03:17:56AM -0400, Jidong Xiao wrote:
> On Wed, Jun 4, 2014 at 3:09 AM, Paolo Bonzini wrote:
> > Il 04/06/2014 03:10, Jidong Xiao ha scritto:
> >
> >> diff --git a/qemu-2.0.0/target-i386/kvm.c.orig
> >> b/qemu-2.0.0/target-i386/kvm.c
> >> index 4389959..b8b282d 100644
> >> -
Properly detect a fault when attempting to store into an invalid
struct timespec pointer.
Signed-off-by: Tom Musta
Reviewed-by: Peter Maydell
---
V2: Peter has observed that there are other call sites that may need to
be fixed. I will address that in future patch(es).
linux-user/syscall.c |
For those target ABIs that use the ipc system call (e.g. POWER),
the third argument is used in the shmat path as a pointer. It
therefore must be declared as an abi_long (versus int) so that
the address bits are not lost in truncation. In fact, all arguments
to do_ipc should be declared as abit_lo
The ELF V2 ABI for PPC64 defines MINSIGSTKSZ as 4096 bytes whereas it was
2048 previously.
Signed-off-by: Tom Musta
---
V2: Define and use TARGET_MINSIGSTKSZ constants from the various
linux-user/$ARCH/syscall.h files (per Peter Maydell's review).
There is still a runtime check for PPC64 since t
The clock_nanosleep syscall is unusual in that it returns positive
numbers in error handling situations, versus returning -1 and setting
errno, or returning a negative errno value. On POWER, the kernel will
set the SO bit of CR0 to indicate failure in a syscall. QEMU has
generic handling to do th
When the ipc system call is used to wrap a semctl system call,
the ptr argument to ipc needs to be dereferenced prior to passing
it to the semctl handler. This is because the fourth argument to
semctl is a union and not a pointer to a union.
Signed-off-by: Tom Musta
---
V2: This is unchanged f
The msgsnd system call takes an argument that describes the message
size (msgsz) and is of type size_t. The system call should set
errno to EINVAL in the event that a negative message size is passed.
Signed-off-by: Tom Musta
Reviewed-by: Peter Maydell
---
linux-user/syscall.c |6 +-
1
The sched_getparam, sched_setparam and sched_setscheduler system
calls take a pointer argument to a sched_param structure. When
this pointer is null, errno should be set to EINVAL.
Signed-off-by: Tom Musta
---
V2: Including sched_setscheduler in the changes per Peter Maydell's
review.
linux-us
The 64 bit PowerPC platforms eliminate the _unused1 and _unused2
elements of the semid_ds structure from . So eliminate
these from the target_semid_ds structure.
Signed-off-by: Tom Musta
---
linux-user/syscall.c |4
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/linux-
The mq_open system call takes an optional struct mq_attr pointer
argument in the fourth position. This pointer is used when O_CREAT
is specified in the flags (second) argument. It may be NULL, in
which case the queue is created with implementation defined attributes.
Change the code to properly
The semun union used in the semctl system call contains both an int (val) and
pointers. In cross-endian situations on 64 bit targets, the value passed to
semctl is an 8 byte (abi_long) value and thus does not have the 4-byte val
field in the correct location. In order to rectify this, the other h
This series of patches is the result of executing the Linux Test Program
(LTP) System Call bucket (https://github.com/linux-test-project/ltp)
on the 64 bit big and little endian linux user mode targets for Power.
Some of the changes are not technically unique to Power, but are effectively
so. For
On Tue, Aug 12, 2014 at 07:46:30PM +0100, Daniel P. Berrange wrote:
> Taking the compression feature - arguably the biggest benefit of that
> is when you distribute disk images. eg if someone provides a root disk
> image on a web server, using compression in qcow2 can dramatically
> lower the downl
On Mon, Aug 11, 2014 at 07:38:50PM -0400, 吴兴博 wrote:
> Hello,
>
> The introduction in the wiki page present several advantages of qcow2
> [1]. But I'm a little confused. I really appreciate if any one can give me
> some help on this :).
>
> (1) Currently the raw format doesn't support COW. In
Currently, if the block device backing the IDE drive is resized,
the information about the device as cached inside of the IDEState
structure is not updated, thus when a guest OS re-queries the drive,
it is unable to see the expanded size.
This patch adds a resize callback to correct this, and mark
On Tue, Aug 12, 2014 at 08:07:55AM -0600, Eric Blake wrote:
> On 08/12/2014 07:45 AM, 吴兴博 wrote:
>
> [please don't top-post on technical lists]
>
> > Thanks for your information. It's really helpful.
> > I think adding a bitmap alongside the raw file ( or just within that file)
>
> Umm, how do y
On 08/08/2014 10:48 AM, Artyom Tarasenko wrote:
> Implement Short Floating-Point Store Instructions as described
> in the chapter 13.5.2 of UltraSPARC-IIi User's Manual.
>
> Particularly this instructions are used by NetBSD 4.0.1+ /sparc64
>
> Signed-off-by: Artyom Tarasenko
> ---
>
> With this
On 08/12/2014 09:59 AM, bharat.bhus...@freescale.com wrote:
>
>
>> -Original Message-
>> From: Alexander Graf [mailto:ag...@suse.de]
>> Sent: Monday, August 11, 2014 3:06 PM
>> To: Eric Auger; eric.au...@st.com; christoffer.d...@linaro.org; qemu-
>> de...@nongnu.org; Phillips Kim-R1AAHA;
Signed-off-by: Kevin Wolf
---
hw/ide/core.c| 4 +++-
tests/ide-test.c | 14 ++
2 files changed, 17 insertions(+), 1 deletion(-)
diff --git a/hw/ide/core.c b/hw/ide/core.c
index db191a6..180ded8 100644
--- a/hw/ide/core.c
+++ b/hw/ide/core.c
@@ -838,7 +838,9 @@ static void ide_fl
On Tue, Aug 12, 2014 at 11:30 AM, Eric Blake wrote:
> On 08/12/2014 08:14 AM, 吴兴博 wrote:
> >>> However FVD seems to have been ignored by community.
> >>
> >> Care to give a pointer to a URL describing the FVD format?
> >>
> >> http://lists.nongnu.org/archive/html/qemu-devel/2011-01/msg00398.html
On 08/12/2014 12:36 PM, Eric Blake wrote:
On 08/12/2014 08:35 AM, Daniel Henrique Barboza wrote:
The curl hardcoded timeout (5 seconds) sometimes is not long
enough depending on the remote server configuration and network
traffic. The user should be able to set how much long he is
willing to wa
On 04.08.14 19:39, Peter Maydell wrote:
On 4 August 2014 17:45, Tom Musta wrote:
The ELF V2 ABI for PPC64 defines MINSIGSTKSZ as 4096 bytes whereas it was
2048 previously.
Alpha and SPARC also have a 4096 byte MINSIGSTKSZ...
Signed-off-by: Tom Musta
diff --git a/linux-user/signal.c b/linu
Hi Dann,
yeah, thanks - let's mark this fixed and open a new one.
** Changed in: qemu
Status: New => Fix Released
** Changed in: qemu (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed
Hello,
On Tue, Aug 12, 2014 at 5:41 AM, Li Liu wrote:
>
> Hi all,
>
> Is anyone there can tell the current status of vhost-net on kvm-arm?
>
> Half a year has passed from Isa Ansharullah asked this question:
> http://www.spinics.net/lists/kvm-arm/msg08152.html
>
> I have found two patches which
On 08/03/14 17:28, Chen Gang wrote:
> In dump_init(), when failure occurs, need notice about 'fd' and memory
> mapping. So call dump_cleanup() for it (need let all initializations at
> front).
>
> Also simplify dump_cleanup(): remove redundant 'ret' and redundant 'fd'
> checking.
>
> Signed-off-b
On 08/12/2014 09:21 AM, Moer Cos wrote:
> help
>
>
> 2014-08-12 23:11 GMT+08:00 :
>
>> Send Qemu-devel mailing list submissions to
>> qemu-devel@nongnu.org
>>
Top-posted replies to a digest message, with no content other than
"help", will not get you any useful response. Please don't r
On 08/12/2014 08:35 AM, Daniel Henrique Barboza wrote:
> The curl hardcoded timeout (5 seconds) sometimes is not long
> enough depending on the remote server configuration and network
> traffic. The user should be able to set how much long he is
> willing to wait for the connection.
>
> Adding a n
On 08/12/2014 08:14 AM, 吴兴博 wrote:
>>> However FVD seems to have been ignored by community.
>>
>> Care to give a pointer to a URL describing the FVD format?
>>
>> http://lists.nongnu.org/archive/html/qemu-devel/2011-01/msg00398.html
>
> This thread could be the clearest message on FVD.
That very
On 12.08.14 17:10, Alexey Kardashevskiy wrote:
On 08/12/2014 07:37 PM, Alexander Graf wrote:
On 12.08.14 02:03, Alexey Kardashevskiy wrote:
On 08/12/2014 03:30 AM, Alexander Graf wrote:
On 11.08.14 17:01, Alexey Kardashevskiy wrote:
On 08/11/2014 10:02 PM, Alexander Graf wrote:
On 31.07.14
On 8/12/2014 9:54 AM, Riku Voipio wrote:
> Hi,
>
> On Mon, Aug 04, 2014 at 11:45:27AM -0500, Tom Musta wrote:
>> This series of patches is the result of executing the Linux Test Program
>> (LTP) System Call bucket (https://github.com/linux-test-project/ltp)
>> on the 64 bit big and little endian l
Hi Gu,
Looks more likely logic ordering to me based on indexes. Don't spend time
looking into it, let me look into it if I have done something wrong and fix
it .
Thanks
Anshul Makkar
On Mon, Aug 11, 2014 at 4:35 PM, Anshul Makkar <
anshul.mak...@profitbricks.com> wrote:
> Hi Gu,
>
> These are
help
2014-08-12 23:11 GMT+08:00 :
> Send Qemu-devel mailing list submissions to
> qemu-devel@nongnu.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.nongnu.org/mailman/listinfo/qemu-devel
> or, via email, send a message with subject or body 'help'
On 08/12/2014 07:37 PM, Alexander Graf wrote:
>
> On 12.08.14 02:03, Alexey Kardashevskiy wrote:
>> On 08/12/2014 03:30 AM, Alexander Graf wrote:
>>> On 11.08.14 17:01, Alexey Kardashevskiy wrote:
On 08/11/2014 10:02 PM, Alexander Graf wrote:
> On 31.07.14 11:34, Alexey Kardashevskiy wrot
Hi,
On Mon, Aug 04, 2014 at 11:45:27AM -0500, Tom Musta wrote:
> This series of patches is the result of executing the Linux Test Program
> (LTP) System Call bucket (https://github.com/linux-test-project/ltp)
> on the 64 bit big and little endian linux user mode targets for Power.
>
> Some of the
Indeed, with qemu 1.5 we did not observed this issue at all.
Sorry, but I don't have the resources at the moment to do the bisecting.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1353947
Title:
Hy
pc_fw_cfg_guest_info() never does anything, because has_pci_info is
always false.
Introduced in commit f8c457b "pc: pass PCI hole ranges to Guests",
disabled in commit 9604f70 "pc: disable pci-info for 1.6", and hasn't
been enabled since. Obviously a dead end. Get of it.
Signed-off-by: Markus A
The curl hardcoded timeout (5 seconds) sometimes is not long
enough depending on the remote server configuration and network
traffic. The user should be able to set how much long he is
willing to wait for the connection.
Adding a new option to set this timeout gives the user this
flexibility. The
Andrey: the bug also occurs when not using '--copy-storage-inc'. I
originally encountered the bug on a pair of servers that share a
glusterfs filesystem. As part of the debugging effort, I took glusterfs
out of the equation to show that it is not the cause of the issue. My
test envirement is theref
Sorry, when the table only had the two entries i drew some bad
assumptions from that, and I also missed the fact that hangs were in the
host kernel.
To be clear, running qemu 1.5 on the same host kernel has no issues with
any guest, while qemu 2.0 causes host kernel to hang (indefinately) with
som
On 12.08.14 15:45, Tom Musta wrote:
These patches fix assorted bugs in the emulation of Power Fixed Point Unit
instructions.
All instructions have been thorougly tested by running millions of random
patterns through actual hardware and comparing the results against QEMU.
The bugs all appear to
On Tue, Aug 12, 2014 at 10:07 AM, Eric Blake wrote:
> On 08/12/2014 07:45 AM, 吴兴博 wrote:
>
> [please don't top-post on technical lists]
>
> Sorry about that..
> > Thanks for your information. It's really helpful.
> > I think adding a bitmap alongside the raw file ( or just within that
> file)
>
On 07/31/2014 09:12 PM, Sanidhya Kashyap wrote:
> No functional change except the variable name -- frequency has been modified
> to period.
This sounds like patch revision information that belongs...
>
> Signed-off-by: Sanidhya Kashyap
> ---
...here.
> hmp-commands.hx | 15 +++
>
On 07/31/2014 09:12 PM, Sanidhya Kashyap wrote:
> Signed-off-by: Sanidhya Kashyap
> ---
> hmp-commands.hx | 14 ++
> hmp.c| 5 +
> hmp.h| 1 +
> qapi-schema.json | 9 +
> qmp-commands.hx | 20
> savevm.c | 14 ++
On 07/31/2014 09:12 PM, Sanidhya Kashyap wrote:
> No functional change except the variable name.
This comment feels more like it is a changelog of what is different from
v4. If so, it belongs...
>
> Signed-off-by: Sanidhya Kashyap
> ---
...here, after the --- separator. It makes no sense in
On 08/12/2014 07:45 AM, 吴兴博 wrote:
[please don't top-post on technical lists]
> Thanks for your information. It's really helpful.
> I think adding a bitmap alongside the raw file ( or just within that file)
Umm, how do you propose to add a bitmap within a raw file? The moment
the file contains
* Dr. David Alan Gilbert (dgilb...@redhat.com) wrote:
> * Sanidhya Kashyap (sanidhya.ii...@gmail.com) wrote:
> > The file not only extracts the bitmap from the file but also draws the
> > figure
> > if required. Currently, figure is drawn for all the bitmaps. Later, I'll
> > make
> > the change t
Fix the check for carry in the srad helper to properly construct
the mask -- a "1ULL" must be used (instead of "1") in order to
get the desired result.
Example:
R3 8000
R4 F3511AD4A2CD4C38
srad 3,3,4
Should *not* set XER[CA] but does without this patch.
Signed-off-by: Tom Musta
---
On 64-bit implementations, the mullwo result is the 64 bit product of
the signed 32 bit operands. Fix the implementation to properly deposit
the upper 32 bits into the target register.
Example:
R3 0407DED115077586
R4 53778DF3CA992E09
mullwo 3,3,4
R3 expected : FB9D02730D7735B6
R3 actual :
Thanks for your information. It's really helpful.
I think adding a bitmap alongside the raw file ( or just within that file)
would be suffice to distinguish between present or in backing file.
The idea in FVD looks similar to 'addcow'---use bitmap but delegating
allocation to FS. However FVD seems
For 64-bit implementations, the mullw result is the 64 bit product
of the sign-extended least significant 32 bits of the source
registers.
Fix the code to properly sign extend the source operands and produce
a 64 bit product.
Example:
R3 002F37A0
R4 41C33D242F816715
mullw 3,3,4
R3 expecte
Fix the code to properly detect overflow; the 128 bit signed
product must have all zeroes or all ones in the first 65 bits
otherwise OV should be set.
Example:
R3 45F086A5D5887509
R4 0002
mulldo 3,3,4
Should set XER[OV].
Signed-off-by: Tom Musta
---
target-ppc/int_helper.c | 14
Hi,
Here is my current wip on the throttle group support.
For the user interface I implemented Stefanha's idea proposed in Stuttgart.
For the throttling algorithm I use a cooperative round robin scheduler.
Classical round robin works with a fixed HZ ticks and it's totaly incompatible
with the t
The rlwimi specification includes the ROTL32 operation, which is defined
to be a left rotation of two copies of the least significant 32 bits of
the source GPR.
The current implementation is incorrect on 64-bit implementations in that
it rotates a single copy of the least significant 32 bits, padd
The rlwinm specification includes the ROTL32 operation, which is defined
to be a left rotation of two copies of the least significant 32 bits of
the source GPR.
The current implementation is incorrect on 64-bit implementations in that
it rotates a single copy of the least significant 32 bits, padd
Group throttling will share ThrottleState between multiple bs.
As a consequence the ThrottleState will be accessed by multiple aio context.
Timers are tied to their aio context so they must go out of the ThrottleState
structure.
This commit pave the way for each bs of a common ThrottleState to h
From: Riku Voipio
The current contents of linux-user git tree at
git://git.linaro.org/people/riku.voipio/qemu.git linux-user-for-upstream
For testing and review. I'm still need to test some (especially my) patches
before sending them in pull request. Since this needs a update in my ltp
test
The rlwnm specification includes the ROTL32 operation, which is defined
to be a left rotation of two copies of the least significant 32 bits of
the source GPR.
The current implementation is incorrect on 64-bit implementations in that
it rotates a single copy of the least significant 32 bits, paddi
For 64 bit implementations, the special case of a shift by zero
should result in the sign extension of the least significant 32 bits
of the source GPR (not a direct copy of the 64 bit source GPR).
Example:
R3 A6212433228F41DC
srawi 3,3,0
R3 expected : 228F41DC
R3 actual : A6212433228F41
The throttle_group_incref increment the refcount of a throttle group given it's
name and return the associated throttle state.
The throttle_group_unref is the mirror function for cleaning up.
Signed-off-by: Benoit Canet
---
include/block/block_int.h | 1 +
include/qemu/throttle-groups.h
1 - 100 of 236 matches
Mail list logo
