On Fri, Mar 24, 2017 at 9:33 PM, Boris Ostrovsky
wrote:
>
>>
>> I think we can all agree that the *ideal* situation would be, for the
>> balloon driver to not immediately hotplug memory so it can add 11 more
>> pages, so maybe I just need to figure out why the balloon driver
>> thinks it needs 11
On Fri, Mar 24, 2017 at 5:10 PM, Konrad Rzeszutek Wilk
wrote:
> On Fri, Mar 24, 2017 at 04:34:23PM -0400, Dan Streetman wrote:
>> On Wed, Mar 22, 2017 at 10:13 PM, Boris Ostrovsky
>> wrote:
>> >
>> >
>> > On 03/22/2017 05:16 PM, Dan Streetman wrote:
>
On Wed, Mar 22, 2017 at 10:13 PM, Boris Ostrovsky
wrote:
>
>
> On 03/22/2017 05:16 PM, Dan Streetman wrote:
>>
>> I have a question about a problem introduced by this commit:
>> c275a57f5ec3056f732843b11659d892235faff7
>> "xen/balloon: Set balloon's in
On Thu, Mar 23, 2017 at 3:56 AM, Juergen Gross wrote:
> On 23/03/17 03:13, Boris Ostrovsky wrote:
>>
>>
>> On 03/22/2017 05:16 PM, Dan Streetman wrote:
>>> I have a question about a problem introduced by this commit:
>>> c275a57f5ec3056f732843b11659d8922
I have a question about a problem introduced by this commit:
c275a57f5ec3056f732843b11659d892235faff7
"xen/balloon: Set balloon's initial state to number of existing RAM pages"
It changed the xen balloon current_pages calculation to start with the
number of physical pages in the system, instead of
On Fri, Jan 13, 2017 at 5:30 PM, Konrad Rzeszutek Wilk
wrote:
> On Fri, Jan 13, 2017 at 03:07:51PM -0500, Dan Streetman wrote:
>> Revert the main part of commit:
>> af42b8d12f8a ("xen: fix MSI setup and teardown for PV on HVM guests")
>>
>> That commit in
On Fri, Jan 13, 2017 at 3:00 PM, Boris Ostrovsky
wrote:
> On 01/13/2017 01:44 PM, Stefano Stabellini wrote:
>> On Fri, 13 Jan 2017, Dan Streetman wrote:
>>> On Wed, Jan 11, 2017 at 6:25 PM, Dan Streetman wrote:
>>>> On Wed, Jan 11, 2017 at 1:46 PM, Stefano Stabel
en.org/archives/html/xen-devel/2017-01/msg00447.html
Fixes: af42b8d12f8a ("xen: fix MSI setup and teardown for PV on HVM guests")
Signed-off-by: Dan Streetman
---
arch/x86/pci/xen.c | 23 +++
1 file changed, 7 insertions(+), 16 deletions(-)
diff --git a/arch/x86/pci/
On Wed, Jan 11, 2017 at 6:25 PM, Dan Streetman wrote:
> On Wed, Jan 11, 2017 at 1:46 PM, Stefano Stabellini
> wrote:
>> On Wed, 11 Jan 2017, Dan Streetman wrote:
>>> On Tue, Jan 10, 2017 at 8:25 PM, Stefano Stabellini
>>> wrote:
>>> > On Tue, 10 Jan 201
On Wed, Jan 11, 2017 at 1:46 PM, Stefano Stabellini
wrote:
> On Wed, 11 Jan 2017, Dan Streetman wrote:
>> On Tue, Jan 10, 2017 at 8:25 PM, Stefano Stabellini
>> wrote:
>> > On Tue, 10 Jan 2017, Dan Streetman wrote:
>> >> On Tue, Jan 10, 2017 at 2:03
On Tue, Jan 10, 2017 at 8:25 PM, Stefano Stabellini
wrote:
> On Tue, 10 Jan 2017, Dan Streetman wrote:
>> On Tue, Jan 10, 2017 at 2:03 PM, Stefano Stabellini
>> wrote:
>> > On Tue, 10 Jan 2017, Dan Streetman wrote:
>> >> On Tue, Jan 10, 2017 at 10:57 AM, Dan S
On Tue, Jan 10, 2017 at 2:03 PM, Stefano Stabellini
wrote:
> On Tue, 10 Jan 2017, Dan Streetman wrote:
>> On Tue, Jan 10, 2017 at 10:57 AM, Dan Streetman wrote:
>> > On Mon, Jan 9, 2017 at 2:30 PM, Stefano Stabellini
>> > wrote:
>> >> On Mon, 9 Jan 2017,
On Tue, Jan 10, 2017 at 10:57 AM, Dan Streetman wrote:
> On Mon, Jan 9, 2017 at 2:30 PM, Stefano Stabellini
> wrote:
>> On Mon, 9 Jan 2017, Konrad Rzeszutek Wilk wrote:
>>> On Mon, Jan 09, 2017 at 10:42:41AM -0500, Dan Streetman wrote:
>>> > On Mon, Jan 9,
On Mon, Jan 9, 2017 at 2:30 PM, Stefano Stabellini
wrote:
> On Mon, 9 Jan 2017, Konrad Rzeszutek Wilk wrote:
>> On Mon, Jan 09, 2017 at 10:42:41AM -0500, Dan Streetman wrote:
>> > On Mon, Jan 9, 2017 at 9:59 AM, Boris Ostrovsky
>> > wrote:
>> > > On 01/
On Mon, Jan 9, 2017 at 9:59 AM, Boris Ostrovsky
wrote:
> On 01/06/2017 08:06 PM, Konrad Rzeszutek Wilk wrote:
>> On Thu, Jan 05, 2017 at 02:28:56PM -0500, Dan Streetman wrote:
>>> Do not read a pci device's msi message data to see if a pirq was
>>> previously conf
use
the same pirq that it had before; but that pirq was allocated to
controller B, and thus the Xen event channel for controller A's re-used
pirq fails to map its irq to that pirq; the hypervisor already has the
pirq mapped elsewhere.
Signed-off-by: Dan Streetman
---
arch/x86/pci/xen.c | 23 +
y previous frontswap implementation that they
replace when registering.
This allows frontswap to successfully manage multiple implementations
by keeping a list of them all.
Signed-off-by: Dan Streetman
---
Changes since v2:
-initialize bitmaps in frontswap_register_ops
-fix comment capitalization
d
On Tue, Jun 2, 2015 at 5:06 PM, Andrew Morton wrote:
> On Mon, 1 Jun 2015 10:22:24 -0400 Dan Streetman wrote:
>
>> Change frontswap single pointer to a singly linked list of frontswap
>> implementations. Update Xen tmem implementation as register no longer
>> returns a
y previous frontswap implementation that they
replace when registering.
This allows frontswap to successfully manage multiple implementations
by keeping a list of them all.
Suggested-by: Andrew Morton
Signed-off-by: Dan Streetman
---
Changes since v1, all per Andrew's suggestions:
-comments add
On Fri, May 29, 2015 at 6:07 PM, Andrew Morton
wrote:
> On Thu, 28 May 2015 16:28:37 -0400 Dan Streetman wrote:
>
>> Change frontswap single pointer to a singly linked list of frontswap
>> implementations. Update Xen tmem implementation as register no longer
>> returns a
y previous frontswap implementation that they
replace when registering.
This allows frontswap to successfully manage multiple implementations
by keeping a list of them all.
Signed-off-by: Dan Streetman
---
drivers/xen/tmem.c| 8 +--
include/linux/frontswap.h | 4 +-
mm/frontswap.c
21 matches
Mail list logo
