Discussion of the implementations of VIRTIO specification
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Jie Deng <jie.deng@intel.com>, Gerd Hoffmann <kraxel@redhat.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
	virtio-comment@lists.oasis-open.org,
	virtio-dev@lists.oasis-open.org, cohuck@redhat.com,
	wsa+renesas@sang-engineering.com,
	andriy.shevchenko@linux.intel.com, yu1.wang@intel.com,
	conghui.chen@intel.com, shuo.a.liu@intel.com
Subject: [virtio-comment] Re: [virtio-dev] Re: [virtio-comment] [PATCH v4] virtio-i2c: add the device specification
Date: Wed, 18 Nov 2020 09:22:01 +0100	[thread overview]
Message-ID: <c146eb06-bd77-eaf2-dd8b-3a82f66b8dc2@redhat.com> (raw)
In-Reply-To: <d20aef28-61cb-61c5-f186-ed6a37467764@intel.com>

On 18/11/20 03:06, Jie Deng wrote:
> Can the "kick" be used for grouping ?  I mean when a write and a read
> are sent by one kick at a time, they will be treated as one
> transaction by default if the host has such a feature bit.

No, the kick is only an advice.  The device is allowed to poll on the 
ring and ignore kicks completely, for example.

Paolo


This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.

In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.

Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/


  reply	other threads:[~2020-11-18  8:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-10  7:31 [virtio-comment] [PATCH v4] virtio-i2c: add the device specification Jie Deng
2020-11-10  8:05 ` Paolo Bonzini
2020-11-10 10:33   ` Michael S. Tsirkin
2020-11-10 10:59     ` Paolo Bonzini
2020-11-12  1:51       ` Jie Deng
2020-11-12  8:54         ` Michael S. Tsirkin
2020-11-13  2:39           ` Jie Deng
2020-11-16  2:12             ` Jie Deng
2020-11-16  8:16               ` Paolo Bonzini
2020-11-17  6:55                 ` Jie Deng
2020-11-17  8:23                   ` Gerd Hoffmann
2020-11-17 15:59                     ` Paolo Bonzini
2020-11-18  1:24                       ` Jie Deng
2020-11-18  2:06                     ` [virtio-comment] Re: [virtio-dev] " Jie Deng
2020-11-18  8:22                       ` Paolo Bonzini [this message]
2020-11-19  1:41                         ` Jie Deng
2020-11-19 15:55                           ` Paolo Bonzini
2020-11-20  1:36                             ` Jie Deng

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c146eb06-bd77-eaf2-dd8b-3a82f66b8dc2@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=cohuck@redhat.com \
    --cc=conghui.chen@intel.com \
    --cc=jie.deng@intel.com \
    --cc=kraxel@redhat.com \
    --cc=mst@redhat.com \
    --cc=shuo.a.liu@intel.com \
    --cc=virtio-comment@lists.oasis-open.org \
    --cc=virtio-dev@lists.oasis-open.org \
    --cc=wsa+renesas@sang-engineering.com \
    --cc=yu1.wang@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox