diff for duplicates of <bad58db98c165a61860827d4e720acf8.squirrel@www.codeaurora.org> diff --git a/a/1.txt b/N1/1.txt index 769161b..7285f5d 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,4 +1,4 @@ -> On Wednesday 28 July 2010, stepanm@codeaurora.org wrote: +> On Wednesday 28 July 2010, stepanm at codeaurora.org wrote: >> > On Wednesday 28 July 2010 00:41:06 Stepan Moskovchenko wrote: >> >> Add support for the System MMUs found on the 8x60 and 8x72 >> >> families of Qualcomm chips. These SMMUs allow virtualization @@ -34,20 +34,3 @@ > Arnd Hi Arnd, - ->From what I have been able to tell, the IOMMU interface was written by -AMD/Intel to allow the kvm code to work with a common IOMMU interface. To -that end, it isn't really a generic IOMMU interface. We have chosen to use -our own interface because it provides us with a lightweight way of -managing mappings for more esoteric MSM-specific use cases. - -These map functions also take into account the way in which we map buffers -that we get from our own physical pool, because the current API was not -intended to deal with prioritized allocation of things like on/off-chip -memory. We are currently evaluating how to use the DMA API with our own -specialized allocator, which has been undergoing some discussion on the -other lists. We would like to use this allocator to maximize TLB -performance, as well as to prioritize the allocation from several -different memory pools. - -Steve diff --git a/a/content_digest b/N1/content_digest index 0a2917d..9424cb6 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -2,18 +2,13 @@ "ref\0201007281039.44883.arnd@arndb.de\0" "ref\0ea4bbdecc271f7fa5749d09645f38c0d.squirrel@www.codeaurora.org\0" "ref\0201007281950.20847.arnd@arndb.de\0" - "From\0stepanm@codeaurora.org\0" - "Subject\0Re: [PATCH 1/2] arm: msm: Add System MMU support.\0" + "From\0stepanm@codeaurora.org (stepanm at codeaurora.org)\0" + "Subject\0[PATCH 1/2] arm: msm: Add System MMU support.\0" "Date\0Wed, 28 Jul 2010 17:58:50 -0700 (PDT)\0" - "To\0Arnd Bergmann <arnd@arndb.de>\0" - "Cc\0linux-arm-kernel@lists.infradead.org" - stepanm@codeaurora.org - linux-arm-msm@vger.kernel.org - dwalker@codeaurora.org - " linux-kernel@vger.kernel.org\0" + "To\0linux-arm-kernel@lists.infradead.org\0" "\00:1\0" "b\0" - "> On Wednesday 28 July 2010, stepanm@codeaurora.org wrote:\n" + "> On Wednesday 28 July 2010, stepanm at codeaurora.org wrote:\n" ">> > On Wednesday 28 July 2010 00:41:06 Stepan Moskovchenko wrote:\n" ">> >> Add support for the System MMUs found on the 8x60 and 8x72\n" ">> >> families of Qualcomm chips. These SMMUs allow virtualization\n" @@ -48,23 +43,6 @@ ">\n" "> \tArnd\n" "\n" - "Hi Arnd,\n" - "\n" - ">From what I have been able to tell, the IOMMU interface was written by\n" - "AMD/Intel to allow the kvm code to work with a common IOMMU interface. To\n" - "that end, it isn't really a generic IOMMU interface. We have chosen to use\n" - "our own interface because it provides us with a lightweight way of\n" - "managing mappings for more esoteric MSM-specific use cases.\n" - "\n" - "These map functions also take into account the way in which we map buffers\n" - "that we get from our own physical pool, because the current API was not\n" - "intended to deal with prioritized allocation of things like on/off-chip\n" - "memory. We are currently evaluating how to use the DMA API with our own\n" - "specialized allocator, which has been undergoing some discussion on the\n" - "other lists. We would like to use this allocator to maximize TLB\n" - "performance, as well as to prioritize the allocation from several\n" - "different memory pools.\n" - "\n" - Steve + Hi Arnd, -277b5de7b905d64384a84b06e44984a6a1cae1872a07d402bcb375b8fd2a00ae +02446bfb23fafc04f3d334160517bd69dad29e06a57263fcb8e7243f562bda03
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.