[lkml]   [2008]   [Oct]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH 2/2] x86: replace BIO_VMERGE_BOUNDARY with BIOVEC_PHYS_MERGEABLE
    On Mon, 27 Oct 2008 20:18:44 +1100
    Jeremy Fitzhardinge <> wrote:

    > FUJITA Tomonori wrote:
    > > I'm not familiar with what Xen does but why can't Xen just override
    > >
    > > Why does Xen need to hook BIOVEC_PHYS_MERGEABLE to the iommu_bio_merge
    > > parameter (as this patch does)? BIOVEC_PHYS_MERGEABLE and the
    > > iommu_bio_merge parameter are not related at all.
    > >
    > No, it doesn't. It was convenient to reuse that mechanism, but I can
    > easily re-add something else (which would be more or less identical).

    I still don't see how Xen needs something like the virtual merge
    (sounds that overriding BIOVEC_PHYS_MERGEABLE perfectly works for Xen)
    or why Xen needs a new boot parameter for it. The virtual merge just
    defines how IOMMUs should work.

     \ /
      Last update: 2008-10-27 10:39    [W:0.019 / U:12.724 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site