> > +if (s->opts->has_show_cursor && s->opts->show_cursor) {
> > +s->null_cursor = NULL; /* default pointer */
> > +} else {
> > +s->null_cursor = gdk_cursor_new_for_display(window_display,
> > +GDK_BLANK_CURSOR);
> > +
On Tue, 2020-02-04 at 10:52 +0100, Klaus Jensen wrote:
> Handling DMA errors gracefully is required for the device to pass the
> block/011 test ("disable PCI device while doing I/O") in the blktests
> suite.
>
> With this patch the device passes the test by retrying "critical"
> transfers (posting
On Fri, Feb 07, 2020 at 04:40:33PM +0900, David Stevens wrote:
> Signed-off-by: David Stevens
> ---
> virtio-gpu.tex | 29 +
> 1 file changed, 29 insertions(+)
>
> diff --git a/virtio-gpu.tex b/virtio-gpu.tex
> index af4ca61..e950ad3 100644
> --- a/virtio-gpu.tex
> ++
On Tue, 2020-02-04 at 10:52 +0100, Klaus Jensen wrote:
> Since clean up of the request qsg/iov has been moved to the common
> nvme_enqueue_req_completion function, there is no need to use a
> stack allocated qsg/iov in nvme_dma_prp.
>
> Signed-off-by: Klaus Jensen
> ---
> hw/block/nvme.c | 18 ++
On Tue, 2020-02-04 at 10:51 +0100, Klaus Jensen wrote:
> This refactors how the device issues asynchronous block backend
> requests. The NvmeRequest now holds a queue of NvmeAIOs that are
> associated with the command. This allows multiple aios to be issued for
> a command. Only when all requests h
On Tue, 2020-02-04 at 10:51 +0100, Klaus Jensen wrote:
> Refactor nvme_map_prp and allow PRPs to be located in the CMB. The logic
> ensures that if some of the PRP is in the CMB, all of it must be located
> there, as per the specification.
To be honest this looks like not refactoring but a bugfix
After discussing, I realise I had a misunderstanding in comment #30 that
I'd like to correct.
I had incorrectly assumed that feeding the PXEBooting KVM guest a zero
length pxelinux.cfg file *instructed* it to boot from the local disk.
I now realise that is incorrect. Feeding the PXEBooting KVM gu
Am 05.02.2020 um 15:00 hat Kevin Wolf geschrieben:
> Am 21.01.2020 um 19:11 hat Kevin Wolf geschrieben:
> > Some QMP command handlers can block the main loop for a relatively long
> > time, for example because they perform some I/O. This is quite nasty.
> > Allowing such handlers to run in a corout
On Wed, 12 Feb 2020 at 06:39, Gavin Shan wrote:
>
> On 2/5/20 10:05 PM, Gavin Shan wrote:
> > This allows to inject SError interrupt, which will be used on receiving
> > QMP/HMP "nmi" command in next patch.
> >
> > Signed-off-by: Gavin Shan
> > ---
> > target/arm/cpu.c| 11 +++
> >
On Wed, 12 Feb 2020 at 06:24, Philippe Mathieu-Daudé wrote:
>
> On 2/11/20 6:37 PM, Peter Maydell wrote:
> > @@ -185,7 +185,7 @@ uint32_t vfp_get_fpscr(CPUARMState *env)
> > void HELPER(vfp_set_fpscr)(CPUARMState *env, uint32_t val)
> > {
> > /* When ARMv8.2-FP16 is not supported, FZ16 i
On Tue, Feb 11, 2020 at 11:31:17AM -0500, Michael S. Tsirkin wrote:
> On Tue, Feb 11, 2020 at 04:20:41PM +, Stefan Hajnoczi wrote:
> > On Mon, Feb 03, 2020 at 12:39:49PM +0100, Sergio Lopez wrote:
> > > On Mon, Feb 03, 2020 at 10:57:44AM +, Daniel P. Berrangé wrote:
> > > > On Mon, Feb 03,
Richard Henderson writes:
> Now that we can pass 7 parameters, do not encode register
> operands within simd_data.
What defines the upper limit? Is it the ABI of the backend or just the
efficiency of implementing the prologue for the call?
> --- a/target/arm/sve_helper.c
> +++ b/target/arm/sve
Richard Henderson writes:
> Extend the vector generator infrastructure to handle
> 5 vector arguments.
>
> Signed-off-by: Richard Henderson
Reviewed-by: Alex Bennée
> ---
> include/tcg/tcg-op-gvec.h | 7 +++
> tcg/tcg-op-gvec.c | 32
> 2 files
Richard Henderson writes:
> On 1/30/20 1:38 PM, Stefan Hajnoczi wrote:
>> From: Salvador Fandino
>>
>> NULL is a valid log filename used to indicate we want to use stderr
>> but qemu_set_log_filename (which is called by bsd-user/main.c) was not
>> handling it correctly.
>>
>> That also made
On Tue, 2020-02-04 at 10:51 +0100, Klaus Jensen wrote:
> Add new fields to the Identify Controller and Identify Namespace data
> structures accoding to NVM Express 1.3d.
>
> NVM Express 1.3d requires the following additional features:
> - addition of the Namespace Identification Descriptor List
On Tue, 2020-02-04 at 10:51 +0100, Klaus Jensen wrote:
> 0x is not an allowed value for NCQR and NSQR in Set Features on
> Number of Queues.
>
> Signed-off-by: Klaus Jensen
> ---
> hw/block/nvme.c | 4
> 1 file changed, 4 insertions(+)
>
> diff --git a/hw/block/nvme.c b/hw/block/nvme.c
On Tue, 2020-02-04 at 10:51 +0100, Klaus Jensen wrote:
> Add a trace call for nvme_enqueue_req_completion.
>
> Also, streamline nvme_identify_ns and nvme_identify_ns_list. They do not
> need to repeat the command, it is already in the trace name.
>
> Signed-off-by: Klaus Jensen
> ---
> hw/block
On Tue, 2020-02-04 at 10:51 +0100, Klaus Jensen wrote:
> Add support for returning a resonable response to Get/Set Features of
> mandatory features.
>
> Signed-off-by: Klaus Jensen
> ---
> hw/block/nvme.c | 57 ---
> hw/block/trace-events | 2 ++
>
On Tue, 2020-02-04 at 10:51 +0100, Klaus Jensen wrote:
> Required for compliance with NVMe revision 1.2.1. See NVM Express 1.2.1,
> Section 5.2 ("Asynchronous Event Request command").
>
> Mostly imported from Keith's qemu-nvme tree. Modified with a max number
> of queued events (controllable with
This test case has the same tests as tests/virtio-blk-test.c except for
tests have block_resize.
Signed-off-by: Coiby Xu
---
tests/libqos/vhost-user-blk.c | 126 ++
tests/libqos/vhost-user-blk.h | 44 +++
tests/vhost-user-blk-test.c | 694 ++
3 files change
On Wed, Feb 12, 2020 at 05:33:06PM +0800, Jason Wang wrote:
>
> On 2020/2/12 下午4:53, Jason Wang wrote:
> >
> > On 2020/2/12 下午4:18, Michael S. Tsirkin wrote:
> > > On Wed, Feb 12, 2020 at 11:39:54AM +0800, Jason Wang wrote:
> > > > On 2020/2/11 下午7:33, Michael S. Tsirkin wrote:
> > > > > On Mon,
vhost-user-blk could have played as vhost-user backend but it only supports raw
file and don't support VIRTIO_BLK_T_DISCARD and VIRTIO_BLK_T_WRITE_ZEROES
operations on raw file (ioctl(fd, BLKDISCARD) is only valid for real
block device).
In the future Kevin's qemu-storage-daemon will be used to re
By making use of libvhost, multiple block device drives can be exported
and each drive can serve multiple clients simultaneously.
Since vhost-user-server needs a block drive to be created first, delay
the creation of this object.
Signed-off-by: Coiby Xu
---
Makefile.target | 1
Previously libvhost dispatch events in its own GMainContext. Now vhost-user
client's kick event can be dispatched in block device drive's AioContext
thus IOThread is supported. And also allow vu_message_read and
vu_kick_cb to be replaced so QEMU can run them as coroutines.
Signed-off-by: Coiby Xu
Sharing QEMU devices via vhost-user protocol
Signed-off-by: Coiby Xu
---
util/Makefile.objs | 3 +
util/vhost-user-server.c | 429 +++
util/vhost-user-server.h | 56 +
3 files changed, 489 insertions(+)
create mode 100644 util/vhost-user-server.c
v3:
* separate generic vhost-user-server code from vhost-user-blk-server
code
* re-write vu_message_read and kick hander function as coroutines to
directly call blk_co_preadv, blk_co_pwritev, etc.
* add aio_context notifier functions to support multi-threading model
* other fixes regardin
On Tue, 2020-02-04 at 10:51 +0100, Klaus Jensen wrote:
> Add support for the Get Log Page command and basic implementations of
> the mandatory Error Information, SMART / Health Information and Firmware
> Slot Information log pages.
>
> In violation of the specification, the SMART / Health Informat
On 2020/2/12 下午4:53, Jason Wang wrote:
On 2020/2/12 下午4:18, Michael S. Tsirkin wrote:
On Wed, Feb 12, 2020 at 11:39:54AM +0800, Jason Wang wrote:
On 2020/2/11 下午7:33, Michael S. Tsirkin wrote:
On Mon, Feb 10, 2020 at 05:05:17PM +0800, Zha Bin wrote:
From: Liu Jiang
The standard virtio-mmi
On Tue, 2020-02-04 at 10:51 +0100, Klaus Jensen wrote:
> It might seem wierd to implement this feature for an emulated device,
> but it is mandatory to support and the feature is useful for testing
> asynchronous event request support, which will be added in a later
> patch.
Absolutely but as the
On Tue, 2020-02-04 at 10:51 +0100, Klaus Jensen wrote:
> This patch splits up nvme_realize into multiple individual functions,
> each initializing a different subset of the device.
>
> Signed-off-by: Klaus Jensen
> ---
> hw/block/nvme.c | 175 +++-
> h
On Tue, 2020-02-04 at 10:51 +0100, Klaus Jensen wrote:
> Required for compliance with NVMe revision 1.2.1. See NVM Express 1.2.1,
> Section 5.1 ("Abort command").
>
> The Abort command is a best effort command; for now, the device always
> fails to abort the given command.
>
> Signed-off-by: Klau
Le 06/02/2020 à 18:38, Eric Blake a écrit :
> Detected by a hang in the libnbd testsuite. If a client requests
> multiple meta contexts (both base:allocation and qemu:dirty-bitmap:x)
> at the same time, our attempt to silence a false-positive warning
> about a potential uninitialized variable intr
On Tue, 2020-02-04 at 10:51 +0100, Klaus Jensen wrote:
> Pull the controller memory buffer check to its own function. The check
> will be used on its own in later patches.
>
> Signed-off-by: Klaus Jensen
> ---
> hw/block/nvme.c | 18 +-
> 1 file changed, 13 insertions(+), 5 delet
On Tue, 2020-02-04 at 10:51 +0100, Klaus Jensen wrote:
> Required for compliance with NVMe revision 1.2.1 or later. See NVM
> Express 1.2.1, Section 5.11 ("Identify command"), Figure 90 and Section
> 7.9 ("NVMe Qualified Names").
>
> This also bumps the supported version to 1.2.1.
>
> Signed-off-
On Wed, Feb 12, 2020 at 05:06:52PM +0800, Jason Wang wrote:
>
> On 2020/2/12 上午11:54, Liu, Jing2 wrote:
> >
> >
> > On 2/11/2020 3:40 PM, Jason Wang wrote:
> > >
> > > On 2020/2/11 下午2:02, Liu, Jing2 wrote:
> > > >
> > > >
> > > > On 2/11/2020 12:02 PM, Jason Wang wrote:
> > > > >
> > > > >
On Tue, 2020-02-04 at 10:51 +0100, Klaus Jensen wrote:
> Not used by the device model but added for completeness. See NVM Express
> 1.2.1, Section 5.11 ("Identify command"), Figure 90 and Figure 93.
>
> Signed-off-by: Klaus Jensen
> ---
> include/block/nvme.h | 48 +++
On Wed, Feb 12, 2020 at 05:03:00PM +0800, Jason Wang wrote:
>
> On 2020/2/11 下午10:00, Michael S. Tsirkin wrote:
> > > Yes, it can work but it may bring extra effort when you want to mask a
> > > vector which is was shared by a lot of queues.
> > >
> > > Thanks
> > >
> > masking should be per vq
On Tue, 2020-02-04 at 10:51 +0100, Klaus Jensen wrote:
> Move device configuration parameters to separate struct to make it
> explicit what is configurable and what is set internally.
>
> Signed-off-by: Klaus Jensen
> ---
> hw/block/nvme.c | 44 ++--
> hw/
On 2/11/20 6:57 PM, Peter Maydell wrote:
On Fri, 7 Feb 2020 at 09:55, Roman Kapl wrote:
Documentation says for WDA '0: Assert WDOG output.' and for SRS
'0: Assert system reset signal.'.
Signed-off-by: Roman Kapl
---
hw/misc/imx2_wdt.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
On Tue, 2020-02-04 at 10:51 +0100, Klaus Jensen wrote:
> Change the prefix of all nvme device related trace events to 'nvme_dev'
> to not clash with trace events from the nvme block driver.
>
> Signed-off-by: Klaus Jensen
> ---
> hw/block/nvme.c | 185 +-
On Tue, 2020-02-04 at 10:51 +0100, Klaus Jensen wrote:
> These break statements was left over when commit 3036a626e9ef ("nvme:
> add Get/Set Feature Timestamp support") was merged.
>
> Signed-off-by: Klaus Jensen
> ---
> hw/block/nvme.c | 4
> 1 file changed, 4 deletions(-)
>
> diff --git
On 2020/2/12 上午11:54, Liu, Jing2 wrote:
On 2/11/2020 3:40 PM, Jason Wang wrote:
On 2020/2/11 下午2:02, Liu, Jing2 wrote:
On 2/11/2020 12:02 PM, Jason Wang wrote:
On 2020/2/11 上午11:35, Liu, Jing2 wrote:
On 2/11/2020 11:17 AM, Jason Wang wrote:
On 2020/2/10 下午5:05, Zha Bin wrote:
From
On 2020/2/11 下午10:00, Michael S. Tsirkin wrote:
Yes, it can work but it may bring extra effort when you want to mask a
vector which is was shared by a lot of queues.
Thanks
masking should be per vq too.
--
Yes, but if the vector is shard by e.g 16 queues, then all those
virtqueues needs
On 2020/2/12 下午4:50, Yuri Benditovich wrote:
Hi Jason,
Can you please review these 2 patches and apply if there are no objections.
Thanks,
Yuri Benditovich
Applied.
Thanks
On Wed, 12 Feb 2020 16:13:28 +0800
Tao Xu wrote:
> Add which features are added or removed in this version. Remove the
> changed model-id in versioned CPU models, to keep the model name
> unchanged at /proc/cpuinfo inside the VM.
>
> Signed-off-by: Tao Xu
> ---
>
> Changes in v2:
> - corre
On 2020/2/12 下午4:18, Michael S. Tsirkin wrote:
On Wed, Feb 12, 2020 at 11:39:54AM +0800, Jason Wang wrote:
On 2020/2/11 下午7:33, Michael S. Tsirkin wrote:
On Mon, Feb 10, 2020 at 05:05:17PM +0800, Zha Bin wrote:
From: Liu Jiang
The standard virtio-mmio devices use notification register to si
Hi Jason,
Can you please review these 2 patches and apply if there are no objections.
Thanks,
Yuri Benditovich
On Wed, Jan 29, 2020 at 6:09 PM Dmitry Fleytman
wrote:
>
>
>
> > On 27 Jan 2020, at 13:54, Yuri Benditovich
> > wrote:
> >
> > Add support for following hash types:
> > IPV6 TCP with
Hi, Richard
Thanks for comments.
On 2020/2/12 14:38, Richard Henderson wrote:
On 2/9/20 11:42 PM, LIU Zhiwei wrote:
+/*
+ * As simd_desc supports at most 256 bytes, and in this implementation,
+ * the max vector group length is 2048 bytes. So split it into two parts.
+ *
+ * The first part is
Hi Hailiang,
Thanks for your replaying and explain in detail.
We will try to use the attachments to enhance memory copy.
However, we have some questions for your replying.
1. As you said, "for each checkpoint, we have to send the whole PVM's
pages To SVM", why the only first checkpoint will tak
> From: Peter Xu
> Sent: Wednesday, February 12, 2020 7:36 AM
> To: Liu, Yi L
> Subject: Re: [RFC v3 16/25] intel_iommu: add PASID cache management
> infrastructure
>
> On Wed, Jan 29, 2020 at 04:16:47AM -0800, Liu, Yi L wrote:
> > From: Liu Yi L
> >
> > This patch adds a PASID cache management
On Wed, Feb 12, 2020 at 11:39:54AM +0800, Jason Wang wrote:
>
> On 2020/2/11 下午7:33, Michael S. Tsirkin wrote:
> > On Mon, Feb 10, 2020 at 05:05:17PM +0800, Zha Bin wrote:
> > > From: Liu Jiang
> > >
> > > The standard virtio-mmio devices use notification register to signal
> > > backend. This wi
Add which features are added or removed in this version. Remove the
changed model-id in versioned CPU models, to keep the model name
unchanged at /proc/cpuinfo inside the VM.
Signed-off-by: Tao Xu
---
Changes in v2:
- correct the note of Cascadelake v3 (Xiaoyao)
---
target/i386/cpu.c | 54 +
Because MPX is being removed from the linux kernel, remove MPX feature
from Denverton.
Signed-off-by: Tao Xu
---
target/i386/cpu.c | 12
1 file changed, 12 insertions(+)
diff --git a/target/i386/cpu.c b/target/i386/cpu.c
index 32efa46852..848c992cd3 100644
--- a/target/i386/cpu.c
+
This series of patches will remove MPX from Denverton, remove Remove
monitor from some CPU models. Add additional information for -cpu help
to indicate the changes in this version of CPU model.
The output is as follows:
./x86_64-softmmu/qemu-system-x86_64 -cpu help | grep "\["
x86 Broadwell-v2
Add additional information for -cpu help to indicate the changes in this
version of CPU model.
Suggested-by: Eduardo Habkost
Signed-off-by: Tao Xu
---
target/i386/cpu.c | 11 +--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git a/target/i386/cpu.c b/target/i386/cpu.c
index 69
Add new version of Snowridge, Denverton, Opteron_G3, EPYC, and Dhyana
CPU model to remove MONITOR/MWAIT feature.
After QEMU/KVM use "-overcommit cpu-pm=on" to expose MONITOR/MWAIT
(commit id 6f131f13e68d648a8e4f083c667ab1acd88ce4cd), the MONITOR/MWAIT
feature in these CPU model is unused.
Signed-
On Fri, Jan 31, 2020 at 11:42:06AM +, Liu, Yi L wrote:
> Hi David,
>
> > From: David Gibson [mailto:da...@gibson.dropbear.id.au]
> > Sent: Friday, January 31, 2020 11:59 AM
> > To: Liu, Yi L
> > Subject: Re: [RFC v3 02/25] hw/iommu: introduce DualStageIOMMUObject
> >
> > On Wed, Jan 29, 2020
On 2020/2/12 0:56, Richard Henderson wrote:
On 2/10/20 8:12 AM, LIU Zhiwei wrote:
static inline void cpu_get_tb_cpu_state(CPURISCVState *env, target_ulong *pc,
-target_ulong *cs_base, uint32_t *flags)
+target_ul
301 - 358 of 358 matches
Mail list logo
