Hello All
I am new QEMU development and wanted to Simulate Atheros Network controller.
I am Running QEMU on x86 machine with underlaying network controller from
Broadcom and
compiled linux kernel based on ARM having Atheros driver support.
I guess there must be mapping at QEMU level calls for
Il 15/01/2014 03:09, Tom Knych ha scritto:
> Doing it with sigprocmask seems good I will send an updated patch
No need, I'll apply this patch.
Paolo
** Changed in: qemu
Status: New => Confirmed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1256546
Title:
qemu-s390x-static: segmentation fault entering chroot
Status in QEMU:
Confirmed
S
On Wed, Jan 15, 2014 at 5:06 PM, Li Guang wrote:
> ping ...
>
> any other comments?
> or new suggestions?
>
No new suggestions from me, but PMM has a point about
load_image_targphys@realize doing exactly whats needed, so something
closer to V1 WRT to that may actually be best.
Regards,
peter
>
On 12/20/2013 01:47 PM, Alexey Kardashevskiy wrote:
> On 12/05/2013 08:39 PM, Alexey Kardashevskiy wrote:
>> On 11/21/2013 03:08 PM, Alexey Kardashevskiy wrote:
>>> Here are few reworks for spapr-pci PHB which I'd like to have to support
>>> VFIO.
>>> QOM, errors printing, traces, nothing really s
ping ...
any other comments?
or new suggestions?
Thanks!
Li Guang wrote:
this blob loader will be used to load a specified
blob into a specified RAM address.
Signed-off-by: Li Guang
Suggested-by: Peter Crosthwaite
---
hw/misc/Makefile.objs |2 +
hw/misc/blob-loader.c |
On 15.01.2014 07:27, Fam Zheng wrote:
On Mon, 01/13 11:21, Peter Lieven wrote:
reopening is currently not supported.
Signed-off-by: Peter Lieven
---
tests/qemu-iotests/020 |5 +
1 file changed, 5 insertions(+)
diff --git a/tests/qemu-iotests/020 b/tests/qemu-iotests/020
index a42f3
On 15.01.2014 07:54, Fam Zheng wrote:
On Mon, 01/13 11:21, Peter Lieven wrote:
Signed-off-by: Peter Lieven
---
tests/qemu-iotests/067.out |8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/tests/qemu-iotests/067.out b/tests/qemu-iotests/067.out
index 8d271cc..79ed
On Mon, 01/13 11:21, Peter Lieven wrote:
> Signed-off-by: Peter Lieven
> ---
> tests/qemu-iotests/067.out |8
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/tests/qemu-iotests/067.out b/tests/qemu-iotests/067.out
> index 8d271cc..79ed90f 100644
> --- a/tests/qemu
Vincenzo,
I'm using a tap interface and in the guest virtual device i see all
offloading features are disabled, even though they are enabled in the
physical device.
Perhaps you can help? See below related information:
Bridge to the physical interface in the host:
--
On Sat, Jan 11, 2014 at 4:08 AM, Peter Maydell wrote:
> On 2 January 2014 07:30, Peter Crosthwaite
> wrote:
>> Added Linux SMP support for the Xilinx Zynq platform (2x CPUs are
>> supported)
>>
>> Signed-off-by: Peter Crosthwaite
>> ---
>> Changed from v3:
>> Author reset
>> s/zynq_cpus/cpus
>>
On Mon, 01/13 11:21, Peter Lieven wrote:
> reopening is currently not supported.
>
> Signed-off-by: Peter Lieven
> ---
> tests/qemu-iotests/020 |5 +
> 1 file changed, 5 insertions(+)
>
> diff --git a/tests/qemu-iotests/020 b/tests/qemu-iotests/020
> index a42f32f..f8a849c 100755
> ---
Ok, more information. The console spews 'lapic increasing min_delta_ns
to ' when this happens.
On Tue, Jan 14, 2014 at 8:31 AM, Marcus Sorensen wrote:
> Does anyone have tips on troubleshooting live migration? I've got
> several E5-2650 servers running in test environment, kernel
On Tue, Jan 14, 2014 at 07:37:09PM -0800, Peter Crosthwaite wrote:
> Use fprintf(stderr instead. This removes dependency of libqemuutil.a
> on the monitor.
>
> We can further justify this change, in that this code path should only
> trigger under a fatal error condition. fprintf-stderr is probably
On Mon, 01/13 15:18, Jeff Cody wrote:
> If the top image to commit is the active layer, and also larger than
> the base image, then an I/O error will likely be returned during
> block-commit.
>
> For instance, if we have a base image with a virtual size 10G, and a
> active layer image of size 20G,
On Tue, Jan 14, 2014 at 08:04:40AM +0100, Sebastian Huber wrote:
> Hello,
>
> maybe this patch can be qualified as trivial?
Hi,
I've applied it, thanks.
Cheers,
Edgar
>
> http://lists.nongnu.org/archive/html/qemu-devel/2013-11/msg03488.html
>
> On 2014-01-07 19:07, Sebastian Huber wrote:
> >
** Tags added: saucy
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1254672
Title:
ps segfaults with qemu-{arm,armel,mips,powerpc}-static
Status in QEMU:
Fix Committed
Status in Linaro QEMU:
Ne
Normally QEMU kvm_arch_get_registers() reads registers and sets a dirty
flag which prevents further registers reading from KVM till
kvm_arch_put_registers() executes and resets the flag.
However if we run QEMU with "-S" ("suspended"), then execute "info cpus"
from the QEMU monitor, we end up with
Fixing patch is on list.
Regards,
Peter
On Wed, Jan 15, 2014 at 1:49 PM, Stefan Hajnoczi wrote:
> On Tue, Jan 14, 2014 at 03:46:24PM +0100, Igor Mammedov wrote:
>> make check
>>
>> ...
>> LINK tests/check-qom-interface
>> libqemuutil.a(qemu-error.o): In function `error_vprintf':
>> /home/imam
On Tue, Jan 14, 2014 at 03:46:24PM +0100, Igor Mammedov wrote:
> make check
>
> ...
> LINK tests/check-qom-interface
> libqemuutil.a(qemu-error.o): In function `error_vprintf':
> /home/imammedo/builds/qemu/util/qemu-error.c:23: undefined reference to
> `cur_mon'
> /home/imammedo/builds/qemu/ut
On Mon, Jan 13, 2014 at 06:47:39PM +0800, Stefan Hajnoczi wrote:
> Propagate the error return value from get_indirect().
>
> Signed-off-by: Stefan Hajnoczi
> ---
> hw/virtio/dataplane/vring.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Fixed commit description as suggested by Markus
Thanks for the test case Martin. Problem confirmed.
The issue is that timer_create allows a number of different callback
mechanisms and I had only implemented the one I need.
Working on it now.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscrib
Use fprintf(stderr instead. This removes dependency of libqemuutil.a
on the monitor.
We can further justify this change, in that this code path should only
trigger under a fatal error condition. fprintf-stderr is probably the
appropriate medium as under a fatal error conidition the monitor itself
On Wed, Jan 15, 2014 at 1:31 PM, Peter Crosthwaite
wrote:
> On Wed, Jan 15, 2014 at 12:55 PM, Andreas Färber wrote:
>> Am 15.01.2014 03:29, schrieb Peter Crosthwaite:
>>> Use fprintf(stderr instead. This removes dependency of libqemuutil.a
>>> on the monitor.
>>>
>>> We can further justify this c
On Wed, Jan 15, 2014 at 12:55 PM, Andreas Färber wrote:
> Am 15.01.2014 03:29, schrieb Peter Crosthwaite:
>> Use fprintf(stderr instead. This removes dependency of libqemuutil.a
>> on the monitor.
>>
>> We can further justify this change, in that this code path should only
>> trigger under a fatal
On Tue, Dec 17, 2013 at 9:19 PM, bkantor <1261...@bugs.launchpad.net> wrote:
> Public bug reported:
>
> trace-backend "simple" generates wrong eventid in trace/generated-
> tracers.c after "disable" property occured in trace-events record.
>
> Result: missing or mixing logs in trace file.
Thanks f
The trace-events "disable" keyword turns an event into a nop at
compile-time. This is important for high-frequency events that can
impact performance.
The "disable" keyword is currently broken in the simple trace backend.
This patch fixes the problem as follows:
Trace events are identified by th
Am 15.01.2014 03:29, schrieb Peter Crosthwaite:
> Use fprintf(stderr instead. This removes dependency of libqemuutil.a
> on the monitor.
>
> We can further justify this change, in that this code path should only
> trigger under a fatal error condition. fprintf-stderr is probably the
> appropriate
Best Regards,
潘穎軒Ying-Shiuan Pan
2014/1/14 Barak Wasserstrom
> Ying-Shiuan Pan,
> Thanks again - please see few questions below.
>
> Regards,
> Barak
>
>
> On Tue, Jan 14, 2014 at 5:37 AM, Ying-Shiuan Pan > wrote:
>
>> Hi, Barak,
>>
>> Hope the following info can help you
>>
>> 1.
>> HOST
On Fri, Jan 10, 2014 at 12:00:31AM +0100, Piotr Karbowski wrote:
> kernel 3.12.5, qemu-1.7.0.
>
> With vhost=on, qemu shortly after start uses all its assigned memory
> (2G for example), without vhost-net enabled it does not go to more
> than 200 MB on my idling test virtual machine. 100% reproduc
Use fprintf(stderr instead. This removes dependency of libqemuutil.a
on the monitor.
We can further justify this change, in that this code path should only
trigger under a fatal error condition. fprintf-stderr is probably the
appropriate medium as under a fatal error conidition the monitor itself
On Tue, Jan 14, 2014 at 04:52:55PM +0100, Lluís Vilanova wrote:
> The header is not necessary, given that the simple backend does not define any
> inlined tracing routines.
>
> Signed-off-by: Lluís Vilanova
> ---
> scripts/tracetool/backend/simple.py |3 ---
> trace/simple.c
于 2014/1/13 18:08, Markus Armbruster 写道:
> Ping^2!
>
> Markus Armbruster writes:
>
>> Ping?
>>
>> Markus Armbruster writes:
>>
>>> [Licensing problem, cc: Anthony]
>>>
>>> Kevin Wolf writes:
>>>
Am 13.12.2013 um 14:31 hat Eric Blake geschrieben:
> On 11/12/2013 06:44 PM, Wenchao Xia w
I think you should appoint the usb bus which according to your usb type, such
as:
-device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2
-device usb-ehci,id=usb1,bus=pci.0,addr=0x4
-device usb-hub,id=hub0,bus=usb.0,port=2
-device usb-tablet,id=input0,bus=usb.0,port=1
On 01/15/2014 01:05 AM, Michael S. Tsirkin wrote:
> On Tue, Jan 14, 2014 at 08:50:54AM -0500, Mike Day wrote:
>>
>> "Michael S. Tsirkin" writes:
>>
>>> On Fri, Jan 10, 2014 at 08:31:36AM -0700, Alex Williamson wrote:
>>
>>> Short term, just assume 48 bits on x86.
>>>
>>> We need to figure out what
On Wed, Jan 15, 2014 at 8:26 AM, Peter Crosthwaite
wrote:
> On Wed, Jan 15, 2014 at 4:22 AM, Luiz Capitulino
> wrote:
>> On Tue, 14 Jan 2014 17:44:51 +0100
>> Kevin Wolf wrote:
>>
>>> Am 14.01.2014 um 04:38 hat Edgar E. Iglesias geschrieben:
>>> > On Tue, Jan 14, 2014 at 09:27:10AM +1000, Peter
On 14 January 2014 23:01, Alexander Graf wrote:
>> Is the underlying issue here that we might have a CPU which is
>> in littleendian mode but in a QEMU executable compiled with
>> TARGET_WORDS_BIGENDIAN ? (If so I can't help feeling that
>> the gdb stub is only the tip of the iceberg for things t
On 14.01.2014, at 23:55, Peter Maydell wrote:
> On 14 January 2014 22:40, Alexander Graf wrote:
>> Uli, I thought ppc64le gdb wasn't finalized yet? What does the gdbstub
>> layout look like? Are all fields the same as ppc64(be) but simply byte
>> swapped - including FPR ones?
>
>> This is quit
On 14 January 2014 22:40, Alexander Graf wrote:
> Uli, I thought ppc64le gdb wasn't finalized yet? What does the gdbstub
> layout look like? Are all fields the same as ppc64(be) but simply byte
> swapped - including FPR ones?
> This is quite invasive (and prone to get wrong). If we really just ha
On 14 January 2014 22:05, Romain Naour wrote:
> This patch adds the emulation for a serial Genius mouse using
> Mouse Systems protocol (5bytes).
> This protocol is compatible with most 3-button serial mouse.
"mice".
It might be helpful to note why we should care, ie if there are
any particularly
On 14.01.2014, at 23:06, Thomas Falcon wrote:
> This patch allows registers to be properly read from and written to
> when using the gdbstub to debug a ppc guest running in little
> endian mode. It accomplishes this goal by byte swapping the values of
> any registers only if the MSR:LE value is
This patch allows registers to be properly read from and written to
when using the gdbstub to debug a ppc guest running in little
endian mode. It accomplishes this goal by byte swapping the values of
any registers only if the MSR:LE value is set and if the host machine
is big endian.
Signed-off-b
On Wed, Jan 15, 2014 at 4:22 AM, Luiz Capitulino wrote:
> On Tue, 14 Jan 2014 17:44:51 +0100
> Kevin Wolf wrote:
>
>> Am 14.01.2014 um 04:38 hat Edgar E. Iglesias geschrieben:
>> > On Tue, Jan 14, 2014 at 09:27:10AM +1000, Peter Crosthwaite wrote:
>> > > Ping,
>> > >
>> > > Has this one been forg
On 14 January 2014 22:06, Thomas Falcon wrote:
> This patch allows registers to be properly read from and written to
> when using the gdbstub to debug a ppc guest running in little
> endian mode. It accomplishes this goal by byte swapping the values of
> any registers only if the MSR:LE value is
This patch adds the emulation for a serial Genius mouse using
Mouse Systems protocol (5bytes).
This protocol is compatible with most 3-button serial mouse.
Signed-off-by: Romain Naour
---
Changes v1 -> v2:
Fixes documentation (Paolo Bonzini)
Fixes typos
backends/Makefile.objs | 2 +-
backen
Hi,
The standard is more like
# A union referencing different chardev backend configuration' info.
#
# @gnmouse: Send mouse data using the Genius protocol (since 2.0).
#
# Since: 1.4
##
but that format would require doucmenting all items. :(
You can leave this out of v2.
However, I'd be happy
This patch allows registers to be properly read from and written to
when using the gdbstub to debug a ppc guest running in little
endian mode. It accomplishes this goal by byte swapping the values of
any registers only if the MSR:LE value is set and if the host machine
is big endian.
Signed-off-
Hi; I notice we still don't seem to have anything up on
the wiki at http://wiki.qemu.org/Planning/1.8 (or even at
/2.0). Any suggestions about what the schedule for the
next release, freeze dates, etc should be?
thanks
-- PMM
On 01/14/2014 12:12 PM, Jeff Cody wrote:
> Having both read-only=on and snapshot=on together does not make sense;
> currently, the read-only argument is effectively ignored for the
> temporary snapshot. To prevent confusion, disallow the usage of both
> 'snapshot=on' and 'read-only=on'.
>
> Signe
On Tue, Jan 14, 2014 at 09:05:31PM +0400, Michael Tokarev wrote:
> 09.01.2014 18:58, Luiz Capitulino wrote:
> > Use sizeof(strucy virtio_balloon_config) instead.
> >
> > --- a/hw/virtio/virtio-balloon.c
> > +++ b/hw/virtio/virtio-balloon.c
> > @@ -263,7 +263,7 @@ static void virtio_balloon_get_con
There is still a small window that occurs when a cancel I/O affects
an asynchronous I/O operation that hasn't started. In other words,
when the residual data length equals the expected data length.
Today, the routine virtio_scsi_command_complete fails because the
VirtIOSCSIReq pointer (from the h
In some cases, an unplug can cause events to be dropped, which
leads to an assertion failure when preparing to notify the guest
kernel.
Signed-off-by: Eric Farman
---
hw/scsi/virtio-scsi.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/hw/scsi/virtio-scsi.c b/hw/scsi/virt
Provide the cancel_io vector for disk devices, to ensure that
all asynchronous I/Os are properly cleaned up of their references.
Signed-off-by: Paolo Bonzini
Signed-off-by: Eric Farman
---
hw/scsi/scsi-disk.c |1 +
1 file changed, 1 insertion(+)
diff --git a/hw/scsi/scsi-disk.c b/hw/scsi/s
In working with hot-plug/unplug of virtio-scsi devices on s390,
we have occasionally noticed some erratic behavior when an unplug
occurs while I/O is in flight. Ideally a device is not being used
when it is removed from a guest configuration, but no guarantee
can be made that this will be the case
Having both read-only=on and snapshot=on together does not make sense;
currently, the read-only argument is effectively ignored for the
temporary snapshot. To prevent confusion, disallow the usage of both
'snapshot=on' and 'read-only=on'.
Signed-off-by: Jeff Cody
---
blockdev.c | 7 +++
1 f
On 12/20/13 06:19, Brad Smith wrote:
On 14/12/13 11:27 PM, Brad Smith wrote:
On 10/12/13 7:49 PM, Brad Smith wrote:
This resolves the build issue with building the ROMs on OpenBSD on x86
archs.
As of OpenBSD 5.3 the compiler builds PIE binaries by default and thus
the
whole OS/packages and so f
On Tue, 14 Jan 2014 21:05:31 +0400
Michael Tokarev wrote:
> 09.01.2014 18:58, Luiz Capitulino wrote:
> > Use sizeof(strucy virtio_balloon_config) instead.
> >
> > --- a/hw/virtio/virtio-balloon.c
> > +++ b/hw/virtio/virtio-balloon.c
> > @@ -263,7 +263,7 @@ static void virtio_balloon_get_config(V
On Mon, Jan 13, 2014 at 12:16:11PM +0100, Paolo Bonzini wrote:
> Il 10/01/2014 23:15, Tom Knych ha scritto:
> > I'll flip the conditional check
> >
> > So I traced thru the code and the one path I saw returning EINTR was:
> >
> > kvm_dev_ioctl_create_vm -> kvm_create_vm -> kvm_init_mmu_notifier -
Hi Alexandre,
On Mon, Mar 25, 2013 at 10:28 PM, Alexandre Kandalintsev
wrote:
> Ok, lets go this way. We will define patterns in bridge.conf like
> ~~~
> allowifname vm*
> ~~~
Do you have any news about this patch?
Regards,
--
William
On Jan14 19:24, Paolo Bonzini wrote:
> See http://lists.gnu.org/archive/html/qemu-devel/2013-03/msg04279.html
> and http://lists.gnu.org/archive/html/qemu-devel/2012-10/msg02149.html
> for previous discussions on this topic.
Thanks for pointing me this out, it's now clear.
--
William
signature.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 14/01/2014 18:40, William Dauchy ha scritto:
>>> I think this was nacked already in the past. You would need to
>>> implement some kind of ACL system like the one that is in place
>>> for bridges. Without it, for example, you could hijack
>>> exi
make qdev_unplug()/device_set_realized() to call hotplug handler's
plug/unplug methods if available and remove not needed anymore
hot(un)plug handling from PCIDevice.
In case if hotplug handler is not available, revert to the legacy
hotplug method.
Signed-off-by: Igor Mammedov
---
v2:
* fix tes
On Tue, 14 Jan 2014 17:44:51 +0100
Kevin Wolf wrote:
> Am 14.01.2014 um 04:38 hat Edgar E. Iglesias geschrieben:
> > On Tue, Jan 14, 2014 at 09:27:10AM +1000, Peter Crosthwaite wrote:
> > > Ping,
> > >
> > > Has this one been forgotten or are there issues? PMM had a small
> > > comment, but he w
>>
>> The address above has already been masked. What you need to do is read
>> the BAR. If the value from the BAR end in '1', its MMIO. If it ends in
>> '10', its RAM. If it ends in '0n' its disabled. The first thing that
>> the PCI software does after reading the BAR is mask off the two low
>> bi
Stefan Weil wrote:
> Am 14.01.2014 18:26, schrieb Michael Tokarev:
>> 14.01.2014 10:00, Stefan Weil wrote:
>>> cpu_physical_memory_set_dirty_lebitmap calls getpageaddr and ffsl which are
>>> unavailable for MinGW. As the function is unused for MinGW, it can simply
>>> be excluded from compilation.
On Tue, Jan 14, 2014 at 12:10 PM, Michael S. Tsirkin wrote:
> On Mon, Jan 13, 2014 at 03:25:16PM +0100, Antonios Motakis wrote:
> > Add structures for passing vhost-user messages over a unix domain socket.
> > This is the equivalent of the existing vhost-kernel ioctls.
> >
> > Connect to the name
On Tue, Jan 14, 2014 at 12:21 PM, Michael S. Tsirkin wrote:
> On Mon, Jan 13, 2014 at 03:25:17PM +0100, Antonios Motakis wrote:
> > Each ioctl request of vhost-kernel has a vhost-user message equivalent,
> > which is sent over the control socket.
> >
> > The general approach is to copy the data f
On Tue, Jan 14, 2014 at 12:16 PM, Michael S. Tsirkin wrote:
> On Mon, Jan 13, 2014 at 03:25:13PM +0100, Antonios Motakis wrote:
> > The unlink option allows the created file to be externally deleted
> > after QEMU is terminated.
> >
> > - unlink=on|off - default on, unlink the file after opening
On Tue, Jan 14, 2014 at 12:33 PM, Michael S. Tsirkin wrote:
> On Mon, Jan 13, 2014 at 03:25:11PM +0100, Antonios Motakis wrote:
> > In this patch series we would like to introduce our approach for putting
> a
> > virtio-net backend in an external userspace process. Our eventual target
> is to
> >
Hello,
On Tue, Jan 14, 2014 at 12:14 PM, Michael S. Tsirkin wrote:
> On Mon, Jan 13, 2014 at 03:25:11PM +0100, Antonios Motakis wrote:
> > In this patch series we would like to introduce our approach for putting
> a
> > virtio-net backend in an external userspace process. Our eventual target
>
Split pcie_cap_slot_hotplug() into hotplug/unplug callbacks
and register them as "hotplug-handler" interface implementation of
PCIE_SLOT device.
Replace pci_bus_hotplug() wiring with setting link on PCI BUS
"hotplug-handler" property to PCI_BRIDGE_DEV device.
Signed-off-by: Igor Mammedov
---
v2:
To suppport reopen(), the .bdrv_reopen_prepare() stub must exist.
iSCSI does not have anything that needs to be done to support reopen,
so we can just implement the _prepare() stub.
Signed-off-by: Jeff Cody
---
block/iscsi.c | 9 +
1 file changed, 9 insertions(+)
diff --git a/block/iscs
Quoting Michael S. Tsirkin (2014-01-12 00:50:13)
> On Fri, Jan 10, 2014 at 09:28:39PM +0100, Laszlo Ersek wrote:
> > On 11/28/13 17:03, Laszlo Ersek wrote:
> > > Mike,
> > >
> > > On 11/27/13 12:57, Gerd Hoffmann wrote:
> > >> Make the 32bit pci hole start at end of ram, so all possible address
>
On Tue, 2014-01-14 at 12:55 -0500, Mike Day wrote:
> On Tue, Jan 14, 2014 at 12:49 PM, Mike Day wrote:
> >>> > > >>>
> >>> > > > Prior to this change, there was no re-map with the
> >>> > > > febe
> >
> >> If we choose not to map them, how do we distinguish them fr
On Tue, Jan 14, 2014 at 12:49 PM, Mike Day wrote:
>>> > > >>>
>>> > > > Prior to this change, there was no re-map with the
>>> > > > febe
>
>> If we choose not to map them, how do we distinguish them from guest RAM?
>> There's no MemoryRegion flag that I'm aware of
On 01/14/2014 10:15 AM, William Dauchy wrote:
> this will permit to specify an interface prefix to the tap instead of the
> default one ("tap")
> this functionnality is useful when you need an easy way to find the
s/functionnality/functionality/
> interfaces attached to a given virtual machine
>
This series adds support for the floating-point and Advanced SIMD
versions of the VRINT family of instructions.
Will Newton (9):
target-arm: Move arm_rmode_to_sf to a shared location.
target-arm: Add AArch32 FP VRINTA, VRINTN, VRINTP and VRINTM
target-arm: Add support for AArch32 FP VRINTR
This function will be needed for AArch32 ARMv8 support, so move it to
helper.c where it can be used by both targets. Also moves the code out
of line, but as it is quite a large function I don't believe this
should be a significant performance impact.
Signed-off-by: Will Newton
---
target-arm/cpu
09.01.2014 18:58, Luiz Capitulino wrote:
> Use sizeof(strucy virtio_balloon_config) instead.
>
> --- a/hw/virtio/virtio-balloon.c
> +++ b/hw/virtio/virtio-balloon.c
> @@ -263,7 +263,7 @@ static void virtio_balloon_get_config(VirtIODevice *vdev,
> uint8_t *config_data)
> config.num_pages = cp
>> > > >>>
>> > > > Prior to this change, there was no re-map with the
>> > > > febe
> If we choose not to map them, how do we distinguish them from guest RAM?
> There's no MemoryRegion flag that I'm aware of to distinguish a ram_ptr
> that points to a chunk of gue
Hello Paolo,
Thanks for your quick reply.
On Jan14 18:31, Paolo Bonzini wrote:
> I think this was nacked already in the past. You would need to
> implement some kind of ACL system like the one that is in place for
> bridges. Without it, for example, you could hijack existing iptables rules.
I
this will permit to specify an interface prefix to the tap instead of the
default one ("tap")
this functionnality is useful when you need an easy way to find the
interfaces attached to a given virtual machine
example:
-net bridge,prefix=tapvmA. -net bridge,prefix=tapvmA.
will create `tapvmA.0` a
Add support for the AArch32 Advanced SIMD VRINTX instruction.
Signed-off-by: Will Newton
---
target-arm/translate.c | 11 ++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/target-arm/translate.c b/target-arm/translate.c
index 5108f6b..b6d11db 100644
--- a/target-arm/trans
Am 14.01.2014 18:26, schrieb Michael Tokarev:
> 14.01.2014 10:00, Stefan Weil wrote:
>> cpu_physical_memory_set_dirty_lebitmap calls getpageaddr and ffsl which are
>> unavailable for MinGW. As the function is unused for MinGW, it can simply
>> be excluded from compilation.
> I applied it to -trivia
do so to avoid not necessary forward declarations and
place typeinfo registration at the file end where it's
usualy expected.
Signed-off-by: Igor Mammedov
---
hw/acpi/piix4.c | 88 +++---
1 files changed, 44 insertions(+), 44 deletions(-)
diff -
Il 14/01/2014 18:15, William Dauchy ha scritto:
> this will permit to specify an interface prefix to the tap instead of the
> default one ("tap")
> this functionnality is useful when you need an easy way to find the
> interfaces attached to a given virtual machine
>
> example:
> -net bridge,prefi
14.01.2014 10:00, Stefan Weil wrote:
> cpu_physical_memory_set_dirty_lebitmap calls getpageaddr and ffsl which are
> unavailable for MinGW. As the function is unused for MinGW, it can simply
> be excluded from compilation.
I applied it to -trivial. But maybe it's better to just move whole thing t
Add support for the AArch32 floating-point VRINTR instruction.
Signed-off-by: Will Newton
---
target-arm/translate.c | 11 +++
1 file changed, 11 insertions(+)
diff --git a/target-arm/translate.c b/target-arm/translate.c
index f688f6d..73e0e8d 100644
--- a/target-arm/translate.c
+++ b/t
Add support for the AArch32 floating-point VRINTX instruction.
Signed-off-by: Will Newton
---
target-arm/translate.c | 11 +++
1 file changed, 11 insertions(+)
diff --git a/target-arm/translate.c b/target-arm/translate.c
index 153d0e6..5108f6b 100644
--- a/target-arm/translate.c
+++ b/t
On Tue, 2014-01-14 at 22:37 +0530, Bandan Das wrote:
> Ccing Markus for the *_once macros
>
> Alex Williamson writes:
>
> > On Tue, 2014-01-14 at 21:45 +0530, Bandan Das wrote:
> >> If the device rom can't be read, report an error to the
> >> user. The guest might try to read the rom contents mo
Ccing Markus for the *_once macros
Alex Williamson writes:
> On Tue, 2014-01-14 at 21:45 +0530, Bandan Das wrote:
>> If the device rom can't be read, report an error to the
>> user. The guest might try to read the rom contents more than
>> once, so introduce macros that print a message only once
If the device rom can't be read, report an error to the
user. The guest might try to read the rom contents more than
once, so introduce macros that print a message only once and
not clutter up the console. This is to alert the user
that the device has a bad state that is causing rom read
failure or
Currently it's possible to make PCIDevice not hotpluggable by using
no_hotplug field of PCIDeviceClass. However it limits this
only to PCI devices and prevents from generalizing hotplug code.
So add similar field to DeviceClass so it could be reused with other
Devices and would allow to replace PC
It will allow to reuse field with different BUSes, reducing code duplication.
Field is intended fot replacing 'hotplug_qdev' field in PCIBus and also
will allow to avoid adding equivalent field to DimmBus with possiblitity
to refactor other BUSes to use it instead of custom field.
In addition once
Get rid of PCIDevice specific PCIDeviceClass.no_hotplug and use
generic DeviceClass.hotpluggable field instead.
Signed-off-by: Igor Mammedov
---
v2:
* move generic hotplug checks to
"qdev: add "hotpluggable" property to Device" patch
* s/hotplugable/hotpluggable/
---
hw/acpi/piix4.c |
changes since v3:
- fixup/add comments as reqused by Peter Crosthwaite
- use error_abort to reduce error handling verbosity
- fix tests/test-qdev-global-props build failure on make check
- rebase on top of current master:133fe7743 (with interface fixes)
Reference to previous version:
http://l
Split piix4_device_hotplug() into hotplug/unplug callbacks
and register them as "hotplug-handler" interface implementation of
PIIX4_PM device.
Replace pci_bus_hotplug() wiring with setting link on
PCI BUS "hotplug-handler" property to PIIX4_PM device.
Signed-off-by: Igor Mammedov
---
v2:
* use e
Thanks, applied to the trivial patches queue.
/mjt
Thanks, applied to the trivial-patches queue.
/mjt
Provide a generic hotplug interface for hotplug handlers.
Intended for replacing hotplug mechanism used by
PCI/PCIE/SHPC code and will be used for memory hotplug.
Signed-off-by: Igor Mammedov
---
v3:
* amend commit description as requested by Peter Crosthwaite
* add doc comments to type definiti
1 - 100 of 203 matches
Mail list logo
