2017-02-17 0:50 GMT+00:00 Fam Zheng :
> On Thu, 02/16 08:58, Franklin Snaipe Mathieu wrote:
>> +p = lock_user_string(arg3)
>> +if (!p) {
>
> Please compile test at least, even if it is a trivial patch.
>
Whoops, sorry, I forgot to re-compile after fixing the checkpatch issu
To maintain consistency at all the places use qemu_madvise wrapper
inplace of madvise call.
Signed-off-by: Pankaj Gupta
---
block/qcow2-cache.c | 2 +-
migration/postcopy-ram.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/block/qcow2-cache.c b/block/qcow2-cache.c
From: Ziyue Yang
Many QEMU monitor commands, like "info lapic", "info tlb" and so on
use mon_get_cpu or related wrappers to access CPU info without checking
whether the CPU exists.
This patch series fix the "info lapic" case, and is the base of the incoming
patch series aiming to eliminate segfau
From: Ziyue Yang
This patch eliminates the segfault caused by accessing CPU that doesn't
exist in hmp command "info lapic", which can be reproduced by
$ qemu-system-x86_64 -nographic -M none -serial none -monitor stdio
and then type "info lapic" into qemu monitor.
Signed-off-by: Ziyue Yang
--
From: Ziyue Yang
Currently mon_get_cpu always dereferences first_cpu without checking
whether it's a valid pointer. This commit adds check before dereferencing,
and reports "No CPU" info if there isn't any CPU then returns NULL.
Signed-off-by: Ziyue Yang
---
monitor.c | 10 +++---
1 file c
In order to support subchannels pass-through, we introduce a s390
subchannel device called "s390-ccw" to hold the real subchannel info.
The s390-ccw devices inherit from the abstract CcwDevice which connect
to the existing virtual-css-bus.
Signed-off-by: Xiao Feng Ren
---
hw/s390x/Makefile.objs
From: Xiao Feng Ren
Implement a basic infrastructure of handling channel I/O instruction
interception for passed through subchannels:
1. Branch the code path of instruction interception handling by
SubChannel type.
2. For a passed-through subchannel, issue the ORB to kernel to do ccw
transl
The patch series introduce a basic channel I/O passthrough
infrastructure based on vfio.
- Focus on supporting dasd-eckd(cu_type/dev_type = 0x3990/0x3390) as
the target device.
- Support new qemu parameters in the style of:
-machine s390-ccw-virtio(,s390-squash-mcss=on|off) \
-device vfi
From: Xiao Feng Ren
The S390 virtual css support already has a mechanism to build virtual
Sub-Channel Information Block and provide virtual subchannels to the
guest. However, to pass-through subchannels to a guest, we need to
introduce a new mechanism to build its schib according to the real
devi
vfio-ccw provides an MMIO region for I/O operations. We fetch its
information via ioctls here, then we can use it performing I/O
instructions and retrieving I/O results later on.
Signed-off-by: Xiao Feng Ren
---
hw/vfio/ccw.c | 52
1 file chan
From: Xiao Feng Ren
We want to support real (i.e. not virtual) channel devices
even for guests that do not support MCSS-E (where guests may
see devices from any channel subsystem image at once). As all
virtio-ccw devices are in css 0xfe (and show up in the default
css 0 for guests not activating
From: Xiao Feng Ren
Introduce a new callback on subchannel to handle ccw-request.
Realize the callback in vfio-ccw device. Besides, resort to
the event notifier handler to handling the ccw-request results.
1. Pread the I/O results via MMIO region.
2. Update the scsw info to guest.
3. Inject an I/
From: Xiao Feng Ren
We use the IOMMU_TYPE1 of VFIO to realize the subchannels
passthrough, implement a vfio based subchannels passthrough
driver called "vfio-ccw".
Support qemu parameters in the style of:
"-device vfio-ccw,sysfsdev=$mdev_file_path,devno=xx.x.'
Signed-off-by: Xiao Feng Ren
The S390 virtual css support already has a mechanism to create a
virtual subchannel and provide it to the guest. However, to
pass-through subchannels to a guest, we need to introduce a new
mechanism to create the subchannel according to the real device
information. Thus we reconstruct css_create_vi
Export the common I/O interfaces those are needed by an I/O
subchannel driver to actually talk to the subchannel.
Signed-off-by: Dong Jia Shi
Reviewed-by: Pierre Morel
---
drivers/s390/cio/cio.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/drivers/s390/cio/cio.c b/drivers/s39
For future code reuse purpose, this decouples the cio code with
the ccw device specific parts from ccw_device_cancel_halt_clear,
and makes a new common I/O interface named cio_cancel_halt_clear.
Signed-off-by: Dong Jia Shi
Reviewed-by: Pierre Morel
---
drivers/s390/cio/cio.c| 59 +++
From: Xiao Feng Ren
vfio-ccw resorts to the eventfd mechanism to communicate with userspace.
We fetch the irqs info via the ioctl VFIO_DEVICE_GET_IRQ_INFO,
register a event notifier to get the eventfd fd which is sent
to kernel via the ioctl VFIO_DEVICE_SET_IRQS, then we can implement
read operat
To make vfio support subchannel devices, we need to leverage the
mediated device framework to create a mediated device for the
subchannel device.
This registers the subchannel device to the mediated device
framework during probe to enable mediated device creation.
Signed-off-by: Dong Jia Shi
Rev
To make vfio support subchannel devices, we need a css driver for
the vfio subchannels. This patch adds a basic vfio-ccw subchannel
driver for this purpose.
To enable VFIO for vfio-ccw, enable S390_CCW_IOMMU config option
and configure VFIO as required.
Signed-off-by: Dong Jia Shi
Acked-by: Pier
Define vfio-ccw device API strings. CCW vendor driver using mediated
device framework should use this string for device_api attribute.
Signed-off-by: Dong Jia Shi
Reviewed-by: Pierre Morel
---
include/uapi/linux/vfio.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/uapi/linux/vfio.
From: Xiao Feng Ren
This is a placeholder for a linux-headers update.
Signed-off-by: Xiao Feng Ren
---
linux-headers/linux/vfio.h | 17 +
linux-headers/linux/vfio_ccw.h | 28
2 files changed, 45 insertions(+)
create mode 100644 linux-headers/li
We implement the basic ccw command handling infrastructure
here:
1. Translate the ccw commands.
2. Issue the translated ccw commands to the device.
3. Once we get the execution result, update the guest SCSW
with it.
Signed-off-by: Dong Jia Shi
Acked-by: Pierre Morel
---
drivers/s390/cio/vfio
Introduce device information about vfio-ccw: VFIO_DEVICE_FLAGS_CCW.
Realize VFIO_DEVICE_GET_REGION_INFO ioctl for vfio-ccw.
Signed-off-by: Dong Jia Shi
Reviewed-by: Pierre Morel
---
drivers/s390/cio/vfio_ccw_ops.c | 78 +
include/uapi/linux/vfio.h |
To provide user-space a set of interfaces to:
1. pass in a ccw program to perform an I/O operation.
2. read back I/O results of the completed I/O operations.
We introduce an MMIO region for the vfio-ccw device here.
This region is defined to content:
1. areas to store arguments that an ssch requir
Realize VFIO_DEVICE_GET_IRQ_INFO ioctl to retrieve
VFIO_CCW_IO_IRQ information.
Realize VFIO_DEVICE_SET_IRQS ioctl to set an eventfd fd for
VFIO_CCW_IO_IRQ. Once a write operation to the ccw_io_region
was performed, trigger a signal on this fd.
Signed-off-by: Dong Jia Shi
Reviewed-by: Pierre Mor
Concurrent-sense data is currently not delivered. This patch stores
the concurrent-sense data to the subchannel if a unit check is pending
and the concurrent-sense bit is enabled. Then a TSCH can retreive the
right IRB data back to the guest.
Signed-off-by: Dong Jia Shi
---
hw/vfio/ccw.c | 7 +++
Although Linux does not use format-0 channel command words (CCW0)
these are a non-optional part of the platform spec, and for the sake
of platform compliance, and possibly some non-Linux guests, we have
to support CCW0.
Making the kernel execute a format 0 channel program is too much hassle
becaus
The current implementation doesn't check if the subchannel is in a
proper device state when handling an event. Let's introduce
a finite state machine to manage the state/event change.
Signed-off-by: Dong Jia Shi
---
drivers/s390/cio/Makefile | 2 +-
drivers/s390/cio/vfio_ccw_drv.c
vfio-ccw: the basic infrastructure
==
Introduction
Here we describe the vfio support for I/O subchannel devices for
Linux/s390. Motivation for vfio-ccw is to passthrough subchannels to a
virtual machine, while vfio is the means.
Different than other h
Add file Documentation/s390/vfio-ccw.txt that includes details
of vfio-ccw.
Signed-off-by: Dong Jia Shi
Acked-by: Pierre Morel
---
Documentation/s390/00-INDEX | 2 +
Documentation/s390/vfio-ccw.txt | 303
2 files changed, 305 insertions(+)
create
Hi
On Thu, Feb 16, 2017 at 12:02 AM Sébastien Frémal <
sebastien.fre...@gmail.com> wrote:
> Hello !
>
> I searched for a forum or a place where questions about QEMU can be asked,
> but I found nothing except mailing lists. If there is a more appropriate
> place for my question, do not hesitate to
Introduce ccwchain structure and helper functions that can be used to
handle a channel program issued from a virtual machine.
The following limitations apply:
1. Supports only prefetch enabled mode.
2. Supports idal(c64) ccw chaining.
3. Supports 4k idaw.
4. Supports ccw1.
5. Supports direct ccw c
Has this problem been fixed in 2012, so that we could close this ticket
now? Or is there still something left to do?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.la
Which version of QEMU were you using? Can you still reproduce this issue
with the latest version of QEMU?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net
Hi,
On 17/02/2017 07:31, vijay.kil...@gmail.com wrote:
> From: Vijaya Kumar K
>
> To Save and Restore ICC_SRE_EL1 register introduce vmstate
> subsection and load only if non-zero.
> Also initialize icc_sre_el1 with to 0x7 in pre_load
> function.
>
> Signed-off-by: Vijaya Kumar K
> ---
> hw/i
Introduce VFIO_DEVICE_RESET ioctl for vfio-ccw to make it possible
to hot-reset the device.
We try to achieve a reset by first disabling the subchannel and
then enabling it again: this should clear all state at the subchannel.
Signed-off-by: Dong Jia Shi
---
drivers/s390/cio/vfio_ccw_ops.c | 47
On 16/02/2017 18:23, Laszlo Ersek wrote:
>> Hi,
>>
>> can you explain exactly which function is missing without
>> -D_XOPEN_SOURCE=500? If it is curses' wide-char functions, why does it
>> fail with musl but not with glibc? Is _XOPEN_SOURCE always defined by
>> glibc if you have _D_GNU_SOURCE?
On 02/17/2017 10:53 AM, zhanghailiang wrote:
Instead of using qemu timer to process the stale packets,
We re-use the colo compare thread to process these packets
by creating a new timeout coroutine.
Besides, since we process all the same vNIC's net connection/packets
in one thread, it is safe
On 16/02/2017 18:23, Laszlo Ersek wrote:
> On 02/16/17 17:58, Paolo Bonzini wrote:
>>
>>
>> On 16/02/2017 17:30, Chad Joan wrote:
>>> Hello,
>>>
>>> This is a one-line patch to the configure script that will allow QEMU to be
>>> built on musl-libc based Linux systems. This problem is only notice
Introduce a singlethreaded workqueue to handle the I/O interrupts.
With the work added to this queue, we store the I/O results to the
io_region of the subchannel, then signal the userspace program to
handle the results.
Signed-off-by: Dong Jia Shi
---
drivers/s390/cio/vfio_ccw_drv.c | 58 +++
On 02/16/2017 03:39 PM, Paolo Bonzini wrote:
>
>
> On 16/02/2017 15:30, fred.kon...@greensocs.com wrote:
>> From: KONRAD Frederic
>>
>> This series allows to execute code from mmio areas.
>> The main goal of this is to be able to run code for example from an SPI
>> device.
>>
>> The three first
Am 17.02.2017 um 01:51 hat Nir Soffer geschrieben:
> Add tests for creating raw image with and without the preallocation
> option.
>
> Signed-off-by: Nir Soffer
Looks good, but 175 is already (multiply) taken. Not making this a
blocker, but I just want to remind everyone to check the mailing lis
Ignore this patch, this was sent again by mistake.
2017-02-17 8:57 GMT+00:00 Franklin Snaipe Mathieu :
> From: "Franklin \"Snaipe\" Mathieu"
>
> The current implementation of the mincore(2) syscall sets errno to
> EFAULT when the region identified by the first two parameters is
> invalid.
>
> Thi
Am 17.02.2017 um 09:06 hat Pankaj Gupta geschrieben:
> To maintain consistency at all the places use qemu_madvise wrapper
> inplace of madvise call.
>
> Signed-off-by: Pankaj Gupta
Reviewed-by: Kevin Wolf
Juan/Dave, if one of you can give an Acked-by, I can take this through
my tree.
Kevin
On Fri, Feb 17, 2017 at 2:30 PM, Auger Eric wrote:
> Hi Vijaya,
>
> On 13/02/2017 13:17, Vijay Kilari wrote:
>> On Tue, Feb 7, 2017 at 8:09 PM, Peter Maydell
>> wrote:
>>> On 31 January 2017 at 16:22, wrote:
From: Vijaya Kumar K
To Save and Restore ICC_SRE_EL1 register Add ICC_
This patch is a follow-up for:
http://lists.nongnu.org/archive/html/qemu-devel/2017-02/msg03647.html
From: "Franklin \"Snaipe\" Mathieu"
The current implementation of the mincore(2) syscall sets errno to
EFAULT when the region identified by the first two parameters is
invalid.
This goes against the man page specification, where mincore(2) should
only fail with EFAULT when the third parameter is
On 02/17/17 09:56, Paolo Bonzini wrote:
>
>
> On 16/02/2017 18:23, Laszlo Ersek wrote:
>> On 02/16/17 17:58, Paolo Bonzini wrote:
>>>
>>>
>>> On 16/02/2017 17:30, Chad Joan wrote:
Hello,
This is a one-line patch to the configure script that will allow QEMU to be
built on musl-
From: "Franklin \"Snaipe\" Mathieu"
The current implementation of the mincore(2) syscall sets errno to
EFAULT when the region identified by the first two parameters is
invalid.
This goes against the man page specification, where mincore(2) should
only fail with EFAULT when the third parameter is
Hi Vijaya,
On 13/02/2017 13:17, Vijay Kilari wrote:
> On Tue, Feb 7, 2017 at 8:09 PM, Peter Maydell
> wrote:
>> On 31 January 2017 at 16:22, wrote:
>>> From: Vijaya Kumar K
>>>
>>> To Save and Restore ICC_SRE_EL1 register Add ICC_SRE_EL1 register
>>> to vmstate and GICv3CPUState struct.
>>>
>
On 17 February 2017 at 06:43, Fam Zheng wrote:
> But your point is taken, we should make the first (or a one-shot)
> contribution as easy as possible.
Yes; we could do with providing a "This page seems very long..."
introduction section. The absolute bare minimum requirements
for a submitter I th
On Feb 17 2017, Richard Henderson wrote:
> On 02/16/2017 09:18 PM, Andreas Schwab wrote:
>> There is no guarantee that the host long double has the same range and
>> precision as floatx80.
>
> Indeed not. However, do you have another plan for implementing the
> trancendentals? I'm quite happy u
On 02/17/17 07:43, Fam Zheng wrote:
> On Thu, 02/16 12:47, Chad Joan wrote:
>> I am glad others are chiming in and might provide better solutions.
>>
>> Honestly, following the instructions at
>> http://wiki.qemu-project.org/Contribute/SubmitAPatch to-the-letter is quite
>> daunting to me, just to
When we build qemu-qmp-ref.txt this causes texinfo to complain several
times:
"Negative repeat count does nothing at
/usr/share/texinfo/Texinfo/Convert/Line.pm line 124."
It also doesn't display correctly, because the "Notes" text disappears
entirely in the HTML version because it thinks there's n
* Kevin Wolf (kw...@redhat.com) wrote:
> Am 17.02.2017 um 09:06 hat Pankaj Gupta geschrieben:
> > To maintain consistency at all the places use qemu_madvise wrapper
> > inplace of madvise call.
> >
> > Signed-off-by: Pankaj Gupta
>
> Reviewed-by: Kevin Wolf
>
> Juan/Dave, if one of you can g
On Fri 17 Feb 2017 09:06:04 AM CET, Pankaj Gupta wrote:
> To maintain consistency at all the places use qemu_madvise wrapper
> inplace of madvise call.
> if (length > 0) {
> -madvise((uint8_t *) t + offset, length, MADV_DONTNEED);
> +qemu_madvise((uint8_t *) t + offset, leng
On Fri, 02/17 10:23, Laszlo Ersek wrote:
> On 02/17/17 07:43, Fam Zheng wrote:
> > On Thu, 02/16 12:47, Chad Joan wrote:
> >> I am glad others are chiming in and might provide better solutions.
> >>
> >> Honestly, following the instructions at
> >> http://wiki.qemu-project.org/Contribute/SubmitAPat
Changes since [v7]
* Paperwork:
- add missing Signed-off-by tags;
- pick up Reviewed-by tags from v7.
Changes since [v6]
* Address review comments:
- re-introduce optical media support;
- rename PCIe Root Ports from pci.* to pcie.*;
- remove reference to GTK+.
Changes si
Instead of having a single sample configuration file,
we now have several:
* q35-emulated.cfg documents the default devices QEMU
adds to a q35 guest and the additional devices that
are pretty much guaranteed to be present in a
physical q35-based machine;
* q35-virtio-graphical.cfg
On Fri, 02/17 09:00, Franklin "Snaipe" Mathieu wrote:
> Ignore this patch, this was sent again by mistake.
Hi Franklin, thanks for the re-submission. Next time please send consecutive
versions as top-level threads instead of replies to previous versions, with
proper 'v2", "v3" tags in the subject.
These are very much like the sample configuration files
for q35, and can be used both as documentation and as
a starting point for creating your own guest.
Two sample configuration files are provided:
* mach-virt-graphical.cfg can be used to start a
fully-featured (USB, graphical console, e
On 17 February 2017 at 08:56, Paolo Bonzini wrote:
> So I do think that if musl wants to support _GNU_SOURCE, it should also
> auto-define;
> however it doesn't, see
> https://git.musl-libc.org/cgit/musl/tree/include/features.h.
Yes, I agree that this looks like a musl bug. I spoke to a musl
de
16.02.2017 17:21, Kevin Wolf wrote:
Am 15.02.2017 um 11:10 hat Vladimir Sementsov-Ogievskiy geschrieben:
Add detailed error messages.
Signed-off-by: Vladimir Sementsov-Ogievskiy
Why not merge this patch into the one that originally introduced the
function?
Just to not create extra work for
16.02.2017 16:48, Fam Zheng wrote:
On Mon, 02/13 12:54, Vladimir Sementsov-Ogievskiy wrote:
When testing migration, auto-generated by qemu node-names differs in
source and destination qemu and migration fails. After this patch,
auto-generated by iotest nodenames will be the same.
What should be
On Thu, Feb 16, 2017 at 5:14 PM Gerd Hoffmann wrote:
> Hi,
>
> Small ccid series which improves the ccid_handle_bulk_out sanity checks.
>
>
looks good,
Reviewed-by: Marc-André Lureau
>
> cheers,
> Gerd
>
> Gerd Hoffmann (3):
> usb-ccid: better bulk_out error handling
> usb-ccid: move
On Thu, 16 Feb 2017 15:15:36 -0800
b...@skyportsystems.com wrote:
> From: Ben Warren
>
> This implements the VM Generation ID feature by passing a 128-bit
> GUID to the guest via a fw_cfg blob.
> Any time the GUID changes, an ACPI notify event is sent to the guest
>
> The user interface is a si
On 17/02/2017 10:17, Laszlo Ersek wrote:
> Of course, *if* that other C library, and the Curses implementation,
> claim compatibility with glibc as far as _GNU_SOURCE goes, *then* I
> fully agree with you. (IOW, it depends on the condition that you
> formulated above, "if musl wants to support _G
On 17/02/2017 11:18, Peter Maydell wrote:
> Defining _XOPEN_SOURCE is easy enough, and I think we should
> do it unconditionally. We should check what effect this has
> on the BSD hosts though I guess. (You could argue that we
> should be defining _XOPEN_SOURCE anyway for the benefit of
> the non
On 16/02/2017 02:31, Gonglei (Arei) wrote:
> And the below patch works for me, I can support max 255 vcpus for WS2012
> with hyper-v enlightenments.
>
> diff --git a/target/i386/kvm.c b/target/i386/kvm.c
> index 27fd050..efe3cbc 100644
> --- a/target/i386/kvm.c
> +++ b/target/i386/kvm.c
> @@ -77
Thanks for your comments. I have below query.
>
> On Fri 17 Feb 2017 09:06:04 AM CET, Pankaj Gupta wrote:
> > To maintain consistency at all the places use qemu_madvise wrapper
> > inplace of madvise call.
>
> > if (length > 0) {
> > -madvise((uint8_t *) t + offset, length, MADV_D
* Pankaj Gupta (pagu...@redhat.com) wrote:
>
> Thanks for your comments. I have below query.
> >
> > On Fri 17 Feb 2017 09:06:04 AM CET, Pankaj Gupta wrote:
> > > To maintain consistency at all the places use qemu_madvise wrapper
> > > inplace of madvise call.
> >
> > > if (length > 0) {
Sure.
I'll see your -O2 and raise you a -c ;)
It went like this:
$ gcc -c first.c -O2
$ gcc -c second.c -O2
$ gcc -c third.c -O2
No complaints from gcc whatsoever (unless I drop the -c, then ld complains
about the undefined reference to main, which I think we all expect).
Just incase you expec
16.02.2017 14:49, Kevin Wolf wrote:
Am 16.02.2017 um 12:25 hat Kevin Wolf geschrieben:
Am 15.02.2017 um 11:10 hat Vladimir Sementsov-Ogievskiy geschrieben:
Auto loading bitmaps are bitmaps stored in the disk image, which should
be loaded when the image is opened and become BdrvDirtyBitmaps for
16.02.2017 15:47, Kevin Wolf wrote:
Sorry, this was sent too early. Next attempt...
Am 16.02.2017 um 12:45 hat Kevin Wolf geschrieben:
Am 15.02.2017 um 11:10 hat Vladimir Sementsov-Ogievskiy geschrieben:
Auto loading bitmaps are bitmaps in Qcow2, with the AUTO flag set. They
are loaded when th
Am 17.02.2017 um 12:46 hat Vladimir Sementsov-Ogievskiy geschrieben:
> 16.02.2017 14:49, Kevin Wolf wrote:
> >Am 16.02.2017 um 12:25 hat Kevin Wolf geschrieben:
> >>Am 15.02.2017 um 11:10 hat Vladimir Sementsov-Ogievskiy geschrieben:
> >>>Auto loading bitmaps are bitmaps stored in the disk image, w
On Fri, 02/17 13:20, Vladimir Sementsov-Ogievskiy wrote:
> 16.02.2017 16:48, Fam Zheng wrote:
> > On Mon, 02/13 12:54, Vladimir Sementsov-Ogievskiy wrote:
> > > When testing migration, auto-generated by qemu node-names differs in
> > > source and destination qemu and migration fails. After this pat
Am 17.02.2017 um 13:07 hat Vladimir Sementsov-Ogievskiy geschrieben:
> 16.02.2017 15:47, Kevin Wolf wrote:
> >Sorry, this was sent too early. Next attempt...
> >
> >Am 16.02.2017 um 12:45 hat Kevin Wolf geschrieben:
> >>Am 15.02.2017 um 11:10 hat Vladimir Sementsov-Ogievskiy geschrieben:
> >>>Auto
Switch to using qcrypto_random_bytes() rather than rand() as
our source of randomness for the BCM2835 RNG.
If qcrypto_random_bytes() fails, we don't want to return the guest a
non-random value in case they're really using it for cryptographic
purposes, so the best we can do is a fatal error. This
16.02.2017 17:08, Kevin Wolf wrote:
Am 15.02.2017 um 11:10 hat Vladimir Sementsov-Ogievskiy geschrieben:
Realize block bitmap storing interface, to allow qcow2 images store
persistent bitmaps.
Signed-off-by: Vladimir Sementsov-Ogievskiy
Reviewed-by: Max Reitz
Reviewed-by: John Snow
Similary
Hi Community,
The Qemu target 'LM3S6965EVB' supports I2C.
I have two firmware versions for a LM3S6965EVB chip that i want to test
with qemu. One is the master and the other is slave.
They use I2C drivers for the LM3S6965EVB chip.
How can i connect these two instances?
I didn't found a simple solu
>
> * Pankaj Gupta (pagu...@redhat.com) wrote:
> >
> > Thanks for your comments. I have below query.
> > >
> > > On Fri 17 Feb 2017 09:06:04 AM CET, Pankaj Gupta wrote:
> > > > To maintain consistency at all the places use qemu_madvise wrapper
> > > > inplace of madvise call.
> > >
> > > >
On Fri 17 Feb 2017 12:30:28 PM CET, Pankaj Gupta wrote:
>> > To maintain consistency at all the places use qemu_madvise wrapper
>> > inplace of madvise call.
>>
>> > -madvise((uint8_t *) t + offset, length, MADV_DONTNEED);
>> > +qemu_madvise((uint8_t *) t + offset, length, QEMU_M
17.02.2017 15:09, Kevin Wolf wrote:
Am 17.02.2017 um 12:46 hat Vladimir Sementsov-Ogievskiy geschrieben:
16.02.2017 14:49, Kevin Wolf wrote:
Am 16.02.2017 um 12:25 hat Kevin Wolf geschrieben:
Am 15.02.2017 um 11:10 hat Vladimir Sementsov-Ogievskiy geschrieben:
Auto loading bitmaps are bitmaps
On 17/02/2017 13:27, Richard Peters wrote:
> Hi Community,
>
> The Qemu target 'LM3S6965EVB' supports I2C.
> I have two firmware versions for a LM3S6965EVB chip that i want to test
> with qemu. One is the master and the other is slave.
> They use I2C drivers for the LM3S6965EVB chip.
There is n
Am 17.02.2017 um 13:40 hat Vladimir Sementsov-Ogievskiy geschrieben:
> 17.02.2017 15:09, Kevin Wolf wrote:
> >Am 17.02.2017 um 12:46 hat Vladimir Sementsov-Ogievskiy geschrieben:
> >>16.02.2017 14:49, Kevin Wolf wrote:
> >>>Am 16.02.2017 um 12:25 hat Kevin Wolf geschrieben:
> Am 15.02.2017 um 1
On Fri 17 Feb 2017 01:30:09 PM CET, Pankaj Gupta wrote:
> I think 'posix_madvise' was added for systems which didnot have
> 'madvise' [...] For the systems which don't have madvise call
> 'posix_madvise' is called which as per discussion is not right thing
> for 'DONTNEED' option. It will not give
CC Dave
On 02/17/17 11:43, Igor Mammedov wrote:
> On Thu, 16 Feb 2017 15:15:36 -0800
> b...@skyportsystems.com wrote:
>
>> From: Ben Warren
>>
>> This implements the VM Generation ID feature by passing a 128-bit
>> GUID to the guest via a fw_cfg blob.
>> Any time the GUID changes, an ACPI notify
On 10 February 2017 at 21:08, Marcin Chojnacki wrote:
> Recent vanilla Raspberry Pi kernels started to make use of
> the hardware random number generator in BCM2835 SoC. As a
> result, those kernels wouldn't work anymore under QEMU
> but rather just freeze during the boot process.
>
> This patch i
17.02.2017 15:21, Kevin Wolf wrote:
Am 17.02.2017 um 13:07 hat Vladimir Sementsov-Ogievskiy geschrieben:
16.02.2017 15:47, Kevin Wolf wrote:
Sorry, this was sent too early. Next attempt...
Am 16.02.2017 um 12:45 hat Kevin Wolf geschrieben:
Am 15.02.2017 um 11:10 hat Vladimir Sementsov-Ogievsk
Am 17.02.2017 um 13:24 hat Vladimir Sementsov-Ogievskiy geschrieben:
> 16.02.2017 17:08, Kevin Wolf wrote:
> >Am 15.02.2017 um 11:10 hat Vladimir Sementsov-Ogievskiy geschrieben:
> >>Realize block bitmap storing interface, to allow qcow2 images store
> >>persistent bitmaps.
> >>
> >>Signed-off-by:
Am 03.02.2017 um 19:31 schrieb Paolo Bonzini:
>
> On 03/02/2017 00:20, Peter Lieven wrote:
>> Am 02.02.2017 um 22:41 schrieb Paolo Bonzini:
>>> On 31/01/2017 07:36, Peter Lieven wrote:
the current implementation fails if we try to freeze an
already frozen filesystem. This can happen if a
Am 17.02.2017 um 13:55 hat Vladimir Sementsov-Ogievskiy geschrieben:
> 17.02.2017 15:21, Kevin Wolf wrote:
>
> Am 17.02.2017 um 13:07 hat Vladimir Sementsov-Ogievskiy geschrieben:
>
> 16.02.2017 15:47, Kevin Wolf wrote:
>
> Sorry, this was sent too early. Next attempt...
On Fri, 17 Feb 2017 13:50:40 +0100
Laszlo Ersek wrote:
> CC Dave
>
> On 02/17/17 11:43, Igor Mammedov wrote:
> > On Thu, 16 Feb 2017 15:15:36 -0800
> > b...@skyportsystems.com wrote:
> >
> >> From: Ben Warren
> >>
> >> This implements the VM Generation ID feature by passing a 128-bit
> >> GUID
On 13 February 2017 at 12:10, Alex Bennée wrote:
> When switching a new vCPU on we want to complete a bunch of the setup
> work before we start scheduling the vCPU thread. To do this cleanly we
> defer vCPU setup to async work which will run the vCPUs execution
> context as the thread is woken up.
On 13 February 2017 at 12:10, Alex Bennée wrote:
> The arm_reset_cpu/set_cpu_on/set_cpu_off() functions do their work
> asynchronously in the target vCPUs context. As a result we need to
> ensure the SRC_SCR reset bits correctly report the reset status at the
> right time. To do this we defer the
On 15 February 2017 at 04:58, P J P wrote:
> Hello Alistair,
>
> +-- On Tue, 14 Feb 2017, Alistair Francis wrote --+
> | On Tue, Feb 14, 2017 at 10:52 AM, P J P wrote:
> | > From: Prasad J Pandit
> | >
> | > In the SDHCI protocol, the transfer mode register value
> | > is used during multi blo
On 14 February 2017 at 18:52, P J P wrote:
> From: Prasad J Pandit
>
> Hello,
>
> In SDHCI protocol, the 'Block Count Enable' bit of the Transfer Mode
> register is used to control 's->blkcnt' value. This bit is not relevant
> in single block transfers. Also, Transfer Mode register value could be
Am 07.02.2017 um 11:13 hat Fam Zheng geschrieben:
> On Wed, 01/25 12:42, Jeff Cody wrote:
> > From: Kevin Wolf
> >
> > This splits the logic in the old parse_chap() function into a part that
> > parses the -iscsi options into the new driver-specific options, and
> > another part that actually app
This series is a rebased series from September 2015, it has been
reviewed but has never reached the master branch.
When DT node names for PCI devices are generated by SLOF,
they are generated according to the type of the device
(for instance, ethernet for virtio-net-pci device).
Node name for hot
On 16 February 2017 at 15:11, Igor Mammedov wrote:
> On Thu, 16 Feb 2017 14:18:05 +
> Peter Maydell wrote:
>> I've always found the object reference semantics somewhat
>> confusing (why does realizing a device add a reference,
>> for instance?). Do we document them anywhere?
> I'm not aware o
1 - 100 of 264 matches
Mail list logo
