From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
Larry Finger <Larry.Finger@lwfinger.net>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH resend 0/4] virt: vboxguest: Fix vboxguest module not working on VMs with more then 4G of RAM
Date: Wed, 18 Apr 2018 17:47:46 +0200 [thread overview]
Message-ID: <20180418154746.GA800@kroah.com> (raw)
In-Reply-To: <20180418132450.11663-1-hdegoede@redhat.com>
On Wed, Apr 18, 2018 at 03:24:46PM +0200, Hans de Goede wrote:
> Hi Greg,
>
> I know you are not entirely happy with the direct get_pages usage in this
> patch-set, but as discussed that is currently the only way to get DMA32
> memory.
>
> Adding a better API for getting DMA32 mem really falls outside of the scope
> of these patches and in the mean time the vboxguest driver is broken on
> VMs with more then 4G RAM, can we please get this bug-fix series merged to
> fix this bug?
I'm on the road all this week, let me catch up with patches next week...
next prev parent reply other threads:[~2018-04-18 15:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-18 13:24 [PATCH resend 0/4] virt: vboxguest: Fix vboxguest module not working on VMs with more then 4G of RAM Hans de Goede
2018-04-18 13:24 ` [PATCH resend 1/4] virt: vbox: Move declarations of vboxguest private functions to private header Hans de Goede
2018-04-18 13:24 ` [PATCH resend 2/4] virt: vbox: Add vbg_req_free() helper function Hans de Goede
2018-04-18 13:24 ` [PATCH resend 3/4] virt: vbox: Use __get_free_pages instead of kmalloc for DMA32 memory Hans de Goede
2018-04-18 13:24 ` [PATCH resend 4/4] virt: vbox: Log an error when we fail to get the host version Hans de Goede
2018-04-18 15:47 ` Greg Kroah-Hartman [this message]
2018-04-23 11:42 ` [PATCH resend 0/4] virt: vboxguest: Fix vboxguest module not working on VMs with more then 4G of RAM Greg Kroah-Hartman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180418154746.GA800@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Larry.Finger@lwfinger.net \
--cc=arnd@arndb.de \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox