search for: ballooned

Some virtio-win drivers contain more files than just *.{cat,inf,sys}. They are filtered out currently, which prevents the drivers from being installed by PnP. Stop filtering driver files by extension, and copy all of them instead. Signed-off-by: Roman Kagan <rkagan@virtuozzo.com> --- v1 -> v2: - update unit test to match the changed behavior v2v/v2v_unit_tests.ml | 202

v2 -> v3 - Don't make a special case for WdfCoInstaller* files. There is a difference of opinion about whether copying these is necessary, but it seems like it is not harmful. Rich.

I think one - maybe final? - problem. How can I tell the difference between drivers for "client" versions of Windows (eg. Windows 7) and server versions of Windows (eg. Windows 2008 Server)? It seems in many or most cases the drivers are identical, eg: $ md5sum viostor/2k12/amd64/* viostor/w8/amd64/* bbe250c13bf891fd7292ccab9908a63a viostor/2k12/amd64/viostor.cat

Hi, I am using centos4 and am trying to build a source kernel dom0 with xen. I cloned a copy of the xen repository and did the following hg clone http://xenbits.xensource.com/xen-2.0.hg cd xen-2.0.hg/xen make dist cd linux-2.6.11-xen0 make ARCH=xen oldconfig make modules make modules_install make install After which point I get the following error : CC drivers/xen/balloon/balloon.o

Instead of trying to split and parse elements from virtio-win paths, use the '*.inf' files supplied with the drivers to control how Windows drivers are installed. The following emails best explain how this works: https://www.redhat.com/archives/libguestfs/2015-October/msg00352.html https://www.redhat.com/archives/libguestfs/2015-November/msg00065.html Currently the product variant (eg.

Adam Litke <alitke at redhat.com> writes: >> On Tue Feb 11 06:01:10 UTC 2014, Rusty Russell wrote: >> Hi all! >> >> We're debating the design of the balloon for the OASIS spec. >> Noone likes the current one, but there are fundamental usage pattern >> questions which we're fumbling with. >> >> So if you know anyone who is

Adam Litke <alitke at redhat.com> writes: >> On Tue Feb 11 06:01:10 UTC 2014, Rusty Russell wrote: >> Hi all! >> >> We're debating the design of the balloon for the OASIS spec. >> Noone likes the current one, but there are fundamental usage pattern >> questions which we're fumbling with. >> >> So if you know anyone who is

https://github.com/rwmjones/libguestfs/tree/rewrite-virtio-copy-drivers Instead of trying to split and parse elements from virtio-win paths, use the '*.inf' files supplied with the drivers to control how Windows drivers are installed. The following emails best explain how this works: https://www.redhat.com/archives/libguestfs/2015-October/msg00352.html

...loon_compaction.c b/mm/balloon_compaction.c > index fcad832..0dd0b0d 100644 > --- a/mm/balloon_compaction.c > +++ b/mm/balloon_compaction.c > @@ -131,43 +131,16 @@ static inline void __putback_balloon_page(struct page *page) > } > > /* __isolate_lru_page() counterpart for a ballooned page */ > -bool balloon_page_isolate(struct page *page) > +bool balloon_page_isolate(struct page *page, isolate_mode_t mode) > { > /* > - * Avoid burning cycles with pages that are yet under __free_pages(), > - * or just got freed under us. > - * > - * In case we '...

...loon_compaction.c b/mm/balloon_compaction.c > index fcad832..0dd0b0d 100644 > --- a/mm/balloon_compaction.c > +++ b/mm/balloon_compaction.c > @@ -131,43 +131,16 @@ static inline void __putback_balloon_page(struct page *page) > } > > /* __isolate_lru_page() counterpart for a ballooned page */ > -bool balloon_page_isolate(struct page *page) > +bool balloon_page_isolate(struct page *page, isolate_mode_t mode) > { > /* > - * Avoid burning cycles with pages that are yet under __free_pages(), > - * or just got freed under us. > - * > - * In case we '...

On 03.02.20 17:18, Alexander Duyck wrote: > On Mon, 2020-02-03 at 08:11 -0500, Michael S. Tsirkin wrote: >> On Thu, Jan 30, 2020 at 11:59:46AM -0800, Tyler Sanderson wrote: >>> >>> On Thu, Jan 30, 2020 at 7:31 AM Wang, Wei W <wei.w.wang at intel.com> wrote: >>> >>> On Thursday, January 30, 2020 11:03 PM, David Hildenbrand wrote: >>>

On 03.02.20 17:18, Alexander Duyck wrote: > On Mon, 2020-02-03 at 08:11 -0500, Michael S. Tsirkin wrote: >> On Thu, Jan 30, 2020 at 11:59:46AM -0800, Tyler Sanderson wrote: >>> >>> On Thu, Jan 30, 2020 at 7:31 AM Wang, Wei W <wei.w.wang at intel.com> wrote: >>> >>> On Thursday, January 30, 2020 11:03 PM, David Hildenbrand wrote: >>>

Hi all! We're debating the design of the balloon for the OASIS spec. Noone likes the current one, but there are fundamental usage pattern questions which we're fumbling with. So if you know anyone who is using it in production? If, so, how? In particular, would you be happy with guests simply giving the host back whatever memory they can spare (as Xen's self-balloon does)?

Hi all! We're debating the design of the balloon for the OASIS spec. Noone likes the current one, but there are fundamental usage pattern questions which we're fumbling with. So if you know anyone who is using it in production? If, so, how? In particular, would you be happy with guests simply giving the host back whatever memory they can spare (as Xen's self-balloon does)?

...eturn false; } diff --git a/mm/balloon_compaction.c b/mm/balloon_compaction.c index fcad832..0dd0b0d 100644 --- a/mm/balloon_compaction.c +++ b/mm/balloon_compaction.c @@ -131,43 +131,16 @@ static inline void __putback_balloon_page(struct page *page) } /* __isolate_lru_page() counterpart for a ballooned page */ -bool balloon_page_isolate(struct page *page) +bool balloon_page_isolate(struct page *page, isolate_mode_t mode) { /* - * Avoid burning cycles with pages that are yet under __free_pages(), - * or just got freed under us. - * - * In case we 'win' a race for a balloon page bein...

Extend the virtio balloon device to support a new feature, this new feature can help to get guest's free pages information, which can be used for live migration optimzation. Signed-off-by: Liang Li <liang.z.li at intel.com> --- balloon.c | 30 ++++++++- hw/virtio/virtio-balloon.c | 81 ++++++++++++++++++++++++-

Hi, I''m working on the following topic from the xen roadmap as a part of an academic project: "Improve interaction between balloon driver and page allocator to avoid memory crunch." I have a few doubts regarding what exactly needs to be done: 1. Should the working of the balloon driver be same as in the case of VMware ESX balloon driver? (

...PageIsolated(page)) { /* raced with isolation */ unlock_page(page); continue; @@ -106,110 +106,53 @@ EXPORT_SYMBOL_GPL(balloon_page_dequeue); #ifdef CONFIG_BALLOON_COMPACTION -static inline void __isolate_balloon_page(struct page *page) +/* __isolate_lru_page() counterpart for a ballooned page */ +bool balloon_page_isolate(struct page *page, isolate_mode_t mode) { struct balloon_dev_info *b_dev_info = balloon_page_device(page); unsigned long flags; spin_lock_irqsave(&b_dev_info->pages_lock, flags); - ClearPagePrivate(page); list_del(&page->lru); b_dev_info...

.../balloon_compaction.c b/mm/balloon_compaction.c > index fcad832..f98a500 100644 > --- a/mm/balloon_compaction.c > +++ b/mm/balloon_compaction.c > @@ -131,7 +131,7 @@ static inline void __putback_balloon_page(struct page *page) > } > > /* __isolate_lru_page() counterpart for a ballooned page */ > -bool balloon_page_isolate(struct page *page) > +bool balloon_page_isolate(struct page *page, isolate_mode_t mode) > { > /* > * Avoid burning cycles with pages that are yet under __free_pages(), > @@ -175,6 +175,9 @@ bool balloon_page_isolate(struct pag...

.../balloon_compaction.c b/mm/balloon_compaction.c > index fcad832..f98a500 100644 > --- a/mm/balloon_compaction.c > +++ b/mm/balloon_compaction.c > @@ -131,7 +131,7 @@ static inline void __putback_balloon_page(struct page *page) > } > > /* __isolate_lru_page() counterpart for a ballooned page */ > -bool balloon_page_isolate(struct page *page) > +bool balloon_page_isolate(struct page *page, isolate_mode_t mode) > { > /* > * Avoid burning cycles with pages that are yet under __free_pages(), > @@ -175,6 +175,9 @@ bool balloon_page_isolate(struct pag...