Michael S. Tsirkin wrote:
> On Mon, Sep 14, 2009 at 12:15:29PM -0500, Anthony Liguori wrote:
>
>> Michael S. Tsirkin wrote:
>>
>>> Hi!
>>> pci bus reset does not seem to clear pci config registers, such as BAR
>>> registers, or memory space enable, of the attached devices: it only
>>> clear
Michael S. Tsirkin wrote:
> On Mon, Sep 14, 2009 at 12:08:55PM -0400, Gregory Haskins wrote:
>> Michael S. Tsirkin wrote:
>>> On Fri, Sep 11, 2009 at 12:00:21PM -0400, Gregory Haskins wrote:
FWIW: VBUS handles this situation via the "memctx" abstraction. IOW,
the memory is not assumed to
Michael S. Tsirkin wrote:
> On Mon, Sep 14, 2009 at 12:08:55PM -0400, Gregory Haskins wrote:
>> For Ira's example, the addresses would represent a physical address on
>> the PCI boards, and would follow any kind of relevant rules for
>> converting a "GPA" to a host accessible address (even if indir
On Mon, Sep 14, 2009 at 12:15:29PM -0500, Anthony Liguori wrote:
> Michael S. Tsirkin wrote:
>> Hi!
>> pci bus reset does not seem to clear pci config registers, such as BAR
>> registers, or memory space enable, of the attached devices: it only
>> clears the interrupt state.
>>
>> This seems wrong,
Michael S. Tsirkin wrote:
> Hi!
> pci bus reset does not seem to clear pci config registers, such as BAR
> registers, or memory space enable, of the attached devices: it only
> clears the interrupt state.
>
> This seems wrong, but easy to fix.
>
I don't think most pci devices reset their config
On Mon, Sep 14, 2009 at 12:08:55PM -0400, Gregory Haskins wrote:
> Michael S. Tsirkin wrote:
> > On Fri, Sep 11, 2009 at 12:00:21PM -0400, Gregory Haskins wrote:
> >> FWIW: VBUS handles this situation via the "memctx" abstraction. IOW,
> >> the memory is not assumed to be a userspace address. Rat
On Mon, Sep 14, 2009 at 12:08:55PM -0400, Gregory Haskins wrote:
> For Ira's example, the addresses would represent a physical address on
> the PCI boards, and would follow any kind of relevant rules for
> converting a "GPA" to a host accessible address (even if indirectly, via
> a dma controller).
Hi!
pci bus reset does not seem to clear pci config registers, such as BAR
registers, or memory space enable, of the attached devices: it only
clears the interrupt state.
This seems wrong, but easy to fix.
Comments?
--
MST
___
Virtualization mailing l
On Wed, Aug 26, 2009 at 08:32:51PM +0900, Ryo Tsuruta wrote:
> Hi All,
>
> As I have notified before, The 1st Linux IO controller Mini-Summit
> will be held in Tokyo Japan on Oct 17 -- day before the 9th Linux
> kernel summit. So I would like to propose the following topics for
> the mini-summit
On Wed, Aug 26 2009 at 7:32am -0400,
Ryo Tsuruta wrote:
> Hi All,
>
> As I have notified before, The 1st Linux IO controller Mini-Summit
> will be held in Tokyo Japan on Oct 17 -- day before the 9th Linux
> kernel summit. So I would like to propose the following topics for
> the mini-summit an
Hi Daniel,
Daniel Walker wrote:
> On Mon, 2009-09-14 at 21:28 +0900, Ryo Tsuruta wrote:
>
> > The list of the patches:
> > [PATCH 1/9] I/O bandwidth controller and BIO tracking
> > [PATCH 2/9] dm-ioband-1.13.0: All-in-one patch
> > [PATCH 3/9] blkio-cgroup-v12: The new page_cgroup framewor
On Mon, 2009-09-14 at 21:28 +0900, Ryo Tsuruta wrote:
> The list of the patches:
> [PATCH 1/9] I/O bandwidth controller and BIO tracking
> [PATCH 2/9] dm-ioband-1.13.0: All-in-one patch
> [PATCH 3/9] blkio-cgroup-v12: The new page_cgroup framework
> [PATCH 4/9] blkio-cgroup-v12: Refactorin
Michael S. Tsirkin wrote:
> On Fri, Sep 11, 2009 at 12:00:21PM -0400, Gregory Haskins wrote:
>> FWIW: VBUS handles this situation via the "memctx" abstraction. IOW,
>> the memory is not assumed to be a userspace address. Rather, it is a
>> memctx-specific address, which can be userspace, or any o
The document of a cgroup support for dm-ioband.
Signed-off-by: Hirokazu Takahashi
Signed-off-by: Ryo Tsuruta
---
Documentation/cgroups/blkio.txt | 314 +++-
1 file changed, 313 insertions(+), 1 deletion(-)
Index: linux-2.6.31/Documentation/cgroups/blkio.tx
Hi Mike,
Mike Snitzer wrote:
> On Wed, Aug 26 2009 at 7:32am -0400,
> Ryo Tsuruta wrote:
>
> > Hi All,
> >
> > As I have notified before, The 1st Linux IO controller Mini-Summit
> > will be held in Tokyo Japan on Oct 17 -- day before the 9th Linux
> > kernel summit. So I would like to propose
With this patch, dm-ioband can work with the blkio-cgroup.
Signed-off-by: Hirokazu Takahashi
Signed-off-by: Ryo Tsuruta
---
drivers/md/dm-ioband-ctl.c | 244 -
drivers/md/dm-ioband-policy.c | 20 +++
drivers/md/dm-ioband-rangebw.c | 13 ++
driv
The document of blkio-cgroup.
Signed-off-by: Hirokazu Takahashi
Signed-off-by: Ryo Tsuruta
---
Documentation/cgroups/00-INDEX |2 +
Documentation/cgroups/blkio.txt | 49
2 files changed, 51 insertions(+)
Index: linux-2.6.31/Documentation/cgroups
This patch contains several hooks that let the blkio-cgroup framework to know
which blkio-cgroup is the owner of a page before starting I/O against the page.
Signed-off-by: Hirokazu Takahashi
Signed-off-by: Ryo Tsuruta
---
fs/buffer.c |2 ++
fs/direct-io.c |2 ++
mm/bounce
The body of blkio-cgroup.
Signed-off-by: Hirokazu Takahashi
Signed-off-by: Ryo Tsuruta
---
include/linux/biotrack.h | 100 ++
include/linux/cgroup_subsys.h |6
init/Kconfig | 13 +
mm/Makefile |1
mm/biotrack.c |
This patch makes the page_cgroup framework be able to be used even if
the compile option of the cgroup memory controller is off.
So blkio-cgroup can use this framework without the memory controller.
Signed-off-by: Hirokazu Takahashi
Signed-off-by: Ryo Tsuruta
---
include/linux/memcontrol.h |
This patch refactors io_context initialization.
Signed-off-by: Hirokazu Takahashi
Signed-off-by: Ryo Tsuruta
---
block/blk-ioc.c | 30 +-
include/linux/iocontext.h |1 +
2 files changed, 18 insertions(+), 13 deletions(-)
Index: linux-2.6.31/block/bl
Hi all,
These are new releases of dm-ioband and blkio-cgroup. The major change
of these releases is that a hierarchical configuration is supported,
a parent cgroup's bandwidth is distributed to its children. The
hierarchical configuration is available when using dm-ioband and
blkio-cgroup together
On Mon, Sep 14, 2009 at 01:57:06PM +0800, Xin, Xiaohui wrote:
> >The irqfd/ioeventfd patches are part of Avi's kvm.git tree:
> >git://git.kernel.org/pub/scm/linux/kernel/git/avi/kvm.git
> >
> >I expect them to be merged by 2.6.32-rc1 - right, Avi?
>
> Michael,
>
> I think I have the kernel patch
23 matches
Mail list logo
