qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Christopher Covington <cov@codeaurora.org>
To: Richard Yao <ryao@gentoo.org>
Cc: kernel@gentoo.org, v9fs-developer@lists.sourceforge.net,
	qemu-devel@nongnu.org, virtualization@lists.linux-foundation.org
Subject: Re: [Qemu-devel] QEMU dies on any attempt to load a Linux kernel module when using a 9P rootfs
Date: Tue, 26 Nov 2013 10:16:54 -0500	[thread overview]
Message-ID: <5294BB66.3060608@codeaurora.org> (raw)
In-Reply-To: <5293C622.4070304@gentoo.org>

Hi Richard,

On 11/25/2013 04:50 PM, Richard Yao wrote:
> I figured out the problem. There is zerocopy IO is being done via DMA to
> a buffer allocated with valloc(). Right now, I am running a hack-fix
> locally so I can get some other stuff done first. I will propose a
> proper fix to the list in a few days.

I've also encountered this issue on a non-QEMU simulator and have been
carrying a disable-zero-copy hack for a few months. Let me know if there's
anything I can help with.

Christopher

-- 
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by the Linux Foundation.

  reply	other threads:[~2013-11-26 15:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-25 15:49 [Qemu-devel] QEMU dies on any attempt to load a Linux kernel module when using a 9P rootfs Richard Yao
2013-11-25 21:50 ` Richard Yao
2013-11-26 15:16   ` Christopher Covington [this message]
2013-11-26 15:38     ` Richard Yao
2013-11-26 15:47       ` Richard Yao
2014-08-21 19:50 ` Christopher Covington
2014-08-22  3:00   ` Richard Yao
2014-08-22  6:27   ` [Qemu-devel] [V9fs-developer] " Dominique Martinet
2014-08-22 12:37     ` Christopher Covington
2014-08-22 12:49       ` Dominique Martinet
2014-08-22 17:54         ` Christopher Covington

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=5294BB66.3060608@codeaurora.org \
    --to=cov@codeaurora.org \
    --cc=kernel@gentoo.org \
    --cc=qemu-devel@nongnu.org \
    --cc=ryao@gentoo.org \
    --cc=v9fs-developer@lists.sourceforge.net \
    --cc=virtualization@lists.linux-foundation.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;
as well as URLs for NNTP newsgroup(s).