lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <871udr1c2f.fsf@rustcorp.com.au> Date: Sat, 12 Jan 2013 10:56:16 +1030 From: Rusty Russell <rusty@...tcorp.com.au> To: Sjur Brændeland <sjurbren@...il.com> Cc: "Michael S. Tsirkin" <mst@...hat.com>, Linus Walleij <linus.walleij@...aro.org>, virtualization@...ts.linux-foundation.org, LKML <linux-kernel@...r.kernel.org>, Ohad Ben-Cohen <ohad@...ery.com> Subject: Re: [RFCv2 00/12] Introduce host-side virtio queue and CAIF Virtio. Sjur Brændeland <sjurbren@...il.com> writes: > How do you see the in-kernel API for this? I would like to see > something similar to my previous patches, where we extend > the virtqueue API. E.g. something like this: > struct virtqueue *vring_new_virtqueueh(unsigned int index, > unsigned int num, > unsigned int vring_align, > struct virtio_device *vdev, > bool weak_barriers, > void *pages, > void (*notify)(struct virtqueue *), > void (*callback)(struct virtqueue *), > const char *name); I was just going to create _kernel variants of all the _user helpers, and let you drive it directly like that. If we get a second in-kernel user, we create wrappers (I'd prefer not to overload struct virtqueue though). Cheers, Rusty. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists