public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: virtio-dev@lists.oasis-open.org,
	virtualization@lists.linux-foundation.org,
	Rusty Russell <rusty@rustcorp.com.au>,
	open list <linux-kernel@vger.kernel.org>,
	"open list:ABI/API" <linux-api@vger.kernel.org>
Subject: Re: [PATCH 1/1] Add virtio-input driver.
Date: Mon, 23 Mar 2015 15:54:01 +0100	[thread overview]
Message-ID: <20150323155106-mutt-send-email-mst@redhat.com> (raw)
In-Reply-To: <1427120855.27137.55.camel@nilsson.home.kraxel.org>

On Mon, Mar 23, 2015 at 03:27:35PM +0100, Gerd Hoffmann wrote:
>   Hi,
> 
> > > > > You are doing leXXX everywhere, that's VERSION_1 dependency.
> > > > > virtio_cread will do byteswaps differently without VERSION_1.
> > > > > Just don't go there.
> 
> > So to clarify, you dislike using __virtio32 in virtio input header?
> 
> Well, as I understand things __virtio32 implies byteorder depends on
> whenever we are using VERSION_1 or not.  And non-transitional drivers
> should not need it as everything is by definition little endian.
> 
> So, yes, your suggestion to just require VERSION_1 in the driver implies
> in my eyes that there should be no reason to use __virtio32 instead of
> __le32.
> 
> Or do I miss something here?
> 
> cheers,
>   Gerd
> 

You are right but then if you do require VERSION_1 then
__virtio32 becomes identical to __le32.
There's some runtime overhead as we check on each access,
but it shouldn't matter here, right?
I guess we could add virtio_cread_le - is this what
you'd like?


-- 
MST

  reply	other threads:[~2015-03-23 14:54 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1426756391-26585-1-git-send-email-kraxel@redhat.com>
2015-03-19  9:13 ` [PATCH 1/1] Add virtio-input driver Gerd Hoffmann
2015-03-19 12:27   ` Michael S. Tsirkin
2015-03-20 10:28     ` Gerd Hoffmann
2015-03-21 22:22       ` Michael S. Tsirkin
2015-03-23  7:53         ` Gerd Hoffmann
2015-03-23 13:44           ` Gerd Hoffmann
2015-03-23 13:51             ` Michael S. Tsirkin
2015-03-23 14:27               ` Gerd Hoffmann
2015-03-23 14:54                 ` Michael S. Tsirkin [this message]
2015-03-23 15:05                   ` Gerd Hoffmann
2015-03-23 16:17                     ` Cornelia Huck
2015-03-23 18:20                     ` Michael S. Tsirkin
2015-03-19 12:29   ` David Herrmann
2015-03-19 16:27     ` Dmitry Torokhov
2015-03-19 17:16       ` David Herrmann
2015-03-20  9:54       ` Gerd Hoffmann
2015-03-20  9:48     ` Gerd Hoffmann
2015-03-20  9:55       ` David Herrmann
2015-03-20 10:36         ` Gerd Hoffmann
2015-03-20 10:43           ` David Herrmann

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=20150323155106-mutt-send-email-mst@redhat.com \
    --to=mst@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --cc=virtio-dev@lists.oasis-open.org \
    --cc=virtualization@lists.linux-foundation.org \
    /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