search for: patchv4

On Tuesday 20 October 2015 18:45:55 Maxim Perevedentsev wrote: > +int64_t > +do_vfs_minimum_size (const mountable_t *mountable) > +{ > + int64_t r; > + > + /* How we set the label depends on the filesystem type. */ Just noticed now: this comment should be really fitting more the new function... :) -- Pino Toscano

On Tue, Oct 20, 2015 at 06:45:54PM +0300, Maxim Perevedentsev wrote: > Tried to make it in accordance with your comments. > > Difference to v1: > Added reply_with_error where necessary. > Changed name get_min_size -> vfs_min_size. > > Difference to v2: > Changed name to vfs_minimum_size. > Changed parsing to xstrtol + STR* macros where possible. > >

On 10/20/2015 07:49 PM, Pino Toscano wrote: > On Tuesday 20 October 2015 18:45:55 Maxim Perevedentsev wrote: >> +int64_t >> +do_vfs_minimum_size (const mountable_t *mountable) >> +{ >> + int64_t r; >> + >> + /* How we set the label depends on the filesystem type. */ > Just noticed now: this comment should be really fitting more the new > function...

I have an issue with btrfs: There's an API > btrfs inspect-internal min-dev-size /sysroot/ But this API is available only in btrfs-progs >= 4.2. Before this, there's no reliable way to get minimum size (I could parse "btrfs filesystem show", but it is veeery inaccurate). Can we require btrfs-progs v4.2? Or how should I work-around this issue? -- Your sincerely, Maxim

On 10/20/2015 08:58 PM, Richard W.M. Jones wrote: > On Tue, Oct 20, 2015 at 08:56:25PM +0300, Maxim Perevedentsev wrote: >> I have an issue with btrfs: >> >> There's an API >>> btrfs inspect-internal min-dev-size /sysroot/ >> But this API is available only in btrfs-progs >= 4.2. >> Before this, there's no reliable way to get minimum size (I

Here is the port of MSI-X support patches to upstream qemu. Please comment or commit. This patchset adds generic support for MSI-X, adds implementation in APIC, and uses MSI-X in virtio-net. Changelog: - since v3 call to resize_region on load split patches a bit differently to address style comments by Glauber update commit message to clarify what msix_support flag does - since v2 rename

Here's a patch series to fix known regressions in virtio_pci, by refactoring code along the lines suggested by Rusty. Changes since v3: whitespace fixed in PATCH 1/2 This is on top of patch virtio: fix memory leak on device removal that has been applied by Rusty. This supercedes patches: [PATCHv3] virtio: recover from vector assignment failure [PATCHv2] virtio: fix double free_irq on

Here is the port of MSI-X support patches to upstream qemu. Please comment or commit. This patchset adds generic support for MSI-X, adds implementation in APIC, and uses MSI-X in virtio-net. Changelog: - since v3 call to resize_region on load split patches a bit differently to address style comments by Glauber update commit message to clarify what msix_support flag does - since v2 rename

Here's a patch series to fix known regressions in virtio_pci, by refactoring code along the lines suggested by Rusty. Changes since v3: whitespace fixed in PATCH 1/2 This is on top of patch virtio: fix memory leak on device removal that has been applied by Rusty. This supercedes patches: [PATCHv3] virtio: recover from vector assignment failure [PATCHv2] virtio: fix double free_irq on

Rusty, could you review and comment on the patches please? Since most of the code deals with virtio from host side, I think it will make sense to merge them through your tree. What do you think? One comment on placement: I put files under a separate vhost directory to avoid confusion with virtio-net which runs in guest. Does this sound sane? If not let me know and I'll move them. Thanks!

Rusty, could you review and comment on the patches please? Since most of the code deals with virtio from host side, I think it will make sense to merge them through your tree. What do you think? One comment on placement: I put files under a separate vhost directory to avoid confusion with virtio-net which runs in guest. Does this sound sane? If not let me know and I'll move them. Thanks!

devices should have the final say over which virtio features they support. E.g. indirect entries may or may not make sense in the context of virtio-console. In particular, for vhost, we do not want to report to guest bits not supported by kernel backend. Move the common bits from virtio-pci to an inline function and let each device call it. No functional changes. Signed-off-by: Michael S.

devices should have the final say over which virtio features they support. E.g. indirect entries may or may not make sense in the context of virtio-console. In particular, for vhost, we do not want to report to guest bits not supported by kernel backend. Move the common bits from virtio-pci to an inline function and let each device call it. No functional changes. Signed-off-by: Michael S.

On Tue, Oct 20, 2015 at 08:56:25PM +0300, Maxim Perevedentsev wrote: > I have an issue with btrfs: > > There's an API > > btrfs inspect-internal min-dev-size /sysroot/ > > But this API is available only in btrfs-progs >= 4.2. > Before this, there's no reliable way to get minimum size (I could > parse "btrfs filesystem show", but it is veeery

This adds support for vhost-net virtio kernel backend. This is not intented for merge. See vhost net patch description for details. This applies on top of commit 47e465f031fc43c53ea8f08fa55cc3482c6435c8 in Avi's tree. It won't apply to tree tip. TODO: rebase. The patchset also includes raw socket backend since I find it useful for testing vhost. When we get to merging, there's no

This adds support for vhost-net virtio kernel backend. This is not intented for merge. See vhost net patch description for details. This applies on top of commit 47e465f031fc43c53ea8f08fa55cc3482c6435c8 in Avi's tree. It won't apply to tree tip. TODO: rebase. The patchset also includes raw socket backend since I find it useful for testing vhost. When we get to merging, there's no

vhost net module wants to do copy to/from user from a kernel thread, which needs use_mm (like what fs/aio has). Move that into mm/ and export to modules. Acked-by: Andrew Morton <akpm at linux-foundation.org> Acked-by: Andrea Arcangeli <aarcange at redhat.com> Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- fs/aio.c | 47

vhost net module wants to do copy to/from user from a kernel thread, which needs use_mm (like what fs/aio has). Move that into mm/ and export to modules. Acked-by: Andrew Morton <akpm at linux-foundation.org> Acked-by: Andrea Arcangeli <aarcange at redhat.com> Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- fs/aio.c | 47

Based on a patch by Mark Wu <dwu at redhat.com> Current index allocation in virtio-blk is based on a monotonically increasing variable "index". This means we'll run out of numbers after a while. It also could cause confusion about the disk name in the case of hot-plugging disks. Change virtio-blk to use ida to allocate index, instead. Signed-off-by: Michael S. Tsirkin

Based on a patch by Mark Wu <dwu at redhat.com> Current index allocation in virtio-blk is based on a monotonically increasing variable "index". This means we'll run out of numbers after a while. It also could cause confusion about the disk name in the case of hot-plugging disks. Change virtio-blk to use ida to allocate index, instead. Signed-off-by: Michael S. Tsirkin