All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 209025] The "VFIO_MAP_DMA failed: Cannot allocate memory" bug is back
Date: Tue, 25 Aug 2020 16:31:53 +0000	[thread overview]
Message-ID: <bug-209025-28872-Lqtk8cYNRl@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-209025-28872@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=209025

--- Comment #8 from Robert M. Muncrief (rmuncrief@humanavance.com) ---
(In reply to Jens Axboe from comment #6)
> (In reply to muncrief from comment #4)
> 
> I'm attaching the patch that should fix this. muncrief, I like to provide
> proper attribution in patches, would you be willing to share your name and
> email so I can add it to the patch? If you prefer not to that's totally fine
> as well, just wanted to give you the option.
> 
> Attaching the patch after this comment.

Awesome Jens! Thank you for figuring this thing out. I'll try the patch as soon
as I'm done with breakfast. And sharing my name and email is fine. I changed my
account to my full name (Robert M. Muncrief).

By the way, for future reference was my assumption that I have to compile the
exact initial kernel version before starting the bisect correct? I switched to
Manjaro three or four years ago, and then Arch about two years ago, but I don't
recall having to do it that way before. But then again I'm not sure if I've
ever bisected the kernel on Arch, it may just have been on Manjaro and Xubuntu.

And hey, don't laugh! I'm old! And my memory sure isn't what it used to be ...
:)

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2020-08-25 16:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-24 16:35 [Bug 209025] New: The "VFIO_MAP_DMA failed: Cannot allocate memory" bug is back bugzilla-daemon
2020-08-24 20:43 ` [Bug 209025] " bugzilla-daemon
2020-08-24 20:57 ` bugzilla-daemon
2020-08-25  0:53 ` bugzilla-daemon
2020-08-25  3:14 ` bugzilla-daemon
2020-08-25  7:26 ` bugzilla-daemon
2020-08-25 14:32 ` bugzilla-daemon
2020-08-25 14:32 ` bugzilla-daemon
2020-08-25 16:31 ` bugzilla-daemon [this message]
2020-08-25 17:09 ` bugzilla-daemon
2020-08-25 17:13 ` bugzilla-daemon
2020-08-25 17:47 ` bugzilla-daemon
2020-08-25 17:55 ` bugzilla-daemon
2020-08-25 18:06 ` bugzilla-daemon

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=bug-209025-28872-Lqtk8cYNRl@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=kvm@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.