Re: [libvirt] [PATCH 16/21] resctrl: Add functions to work with resctrl allocations

2017-11-21 Thread Pavel Hrdina
On Tue, Nov 21, 2017 at 10:49:29AM +0100, Martin Kletzander wrote: > On Wed, Nov 15, 2017 at 07:14:28PM +0100, Pavel Hrdina wrote: > > On Mon, Nov 13, 2017 at 09:50:31AM +0100, Martin Kletzander wrote: > > > With this commit we finally have a way to read and manipulate basic > > > resctrl > > > se

Re: [libvirt] [PATCH 16/21] resctrl: Add functions to work with resctrl allocations

2017-11-21 Thread Martin Kletzander
On Wed, Nov 15, 2017 at 07:14:28PM +0100, Pavel Hrdina wrote: On Mon, Nov 13, 2017 at 09:50:31AM +0100, Martin Kletzander wrote: With this commit we finally have a way to read and manipulate basic resctrl settings. Locking is done only on exposed functions that read/write from/to resctrlfs. No

Re: [libvirt] [PATCH 16/21] resctrl: Add functions to work with resctrl allocations

2017-11-15 Thread John Ferlan
[...] >> /* Info-related functions */ >> int >> virResctrlGetInfo(virResctrlInfoPtr *resctrl) >> @@ -318,3 +465,866 @@ virResctrlInfoGetCache(virResctrlInfoPtr resctrl, >> VIR_FREE(*controls); >> goto cleanup; >> } >> + >> + >> +/* Alloc-related functions */ >> +static virResctrlAll

Re: [libvirt] [PATCH 16/21] resctrl: Add functions to work with resctrl allocations

2017-11-15 Thread Martin Kletzander
On Wed, Nov 15, 2017 at 01:17:56PM -0500, John Ferlan wrote: [...] Two blank lines (multiple instances in new functions) I tried keeping this one more organized, two lines between groups of functions, one line between functions in the same group.  But I can do two everywhere, the fact that

Re: [libvirt] [PATCH 16/21] resctrl: Add functions to work with resctrl allocations

2017-11-15 Thread John Ferlan
[...] >> >> Two blank lines (multiple instances in new functions) >> > > I tried keeping this one more organized, two lines between groups of > functions, one line between functions in the same group.  But I can do > two everywhere, the fact that I don't fully agree is irrelevant > (unfortunatel

Re: [libvirt] [PATCH 16/21] resctrl: Add functions to work with resctrl allocations

2017-11-15 Thread Pavel Hrdina
On Mon, Nov 13, 2017 at 09:50:31AM +0100, Martin Kletzander wrote: > With this commit we finally have a way to read and manipulate basic resctrl > settings. Locking is done only on exposed functions that read/write from/to > resctrlfs. Not in fuctions that are exposed in virresctrlpriv.h as those

Re: [libvirt] [PATCH 16/21] resctrl: Add functions to work with resctrl allocations

2017-11-15 Thread Martin Kletzander
On Tue, Nov 14, 2017 at 06:52:48PM -0500, John Ferlan wrote: On 11/13/2017 03:50 AM, Martin Kletzander wrote: With this commit we finally have a way to read and manipulate basic resctrl settings. Locking is done only on exposed functions that read/write from/to resctrlfs. Not in fuctions tha

Re: [libvirt] [PATCH 16/21] resctrl: Add functions to work with resctrl allocations

2017-11-14 Thread John Ferlan
On 11/13/2017 03:50 AM, Martin Kletzander wrote: > With this commit we finally have a way to read and manipulate basic resctrl > settings. Locking is done only on exposed functions that read/write from/to > resctrlfs. Not in fuctions that are exposed in virresctrlpriv.h as those are functions

[libvirt] [PATCH 16/21] resctrl: Add functions to work with resctrl allocations

2017-11-13 Thread Martin Kletzander
With this commit we finally have a way to read and manipulate basic resctrl settings. Locking is done only on exposed functions that read/write from/to resctrlfs. Not in fuctions that are exposed in virresctrlpriv.h as those are only supposed to be used from tests. Signed-off-by: Martin Kletzand