From: 魏振伟 <weizhenwei-hf@loongson.cn>
To: qemu-devel@nongnu.org
Cc: PengFei <pengfei-hf@loongson.cn>
Subject: [Qemu-devel] Ask about patching our MIPS work to Qemu main branch
Date: Tue, 10 Mar 2015 12:00:17 +0800 (GMT+08:00) [thread overview]
Message-ID: <37c8316.c54.14c01d71edf.Coremail.weizhenwei-hf@loongson.cn> (raw)
[-- Attachment #1: Type: text/plain, Size: 518 bytes --]
Hi, there,
We are software engineers of Loongson.Inc，a computer company design
and produce MIPS-compatible computers located in China。
Currently we use Qemu to run X86-64 network programs such as snort on MIPS platform.
During Qemu running on MIPS, we found some Qemu bugs such as pagesize,
memory access, multi-thread, etc. And now we have fixed some of them.
We wonder if these bug patch could port to Qeme official main branch,
so we write to ask your advice.
Best Regards~
Weizhenwei
2015.03.10
[-- Attachment #2: Type: text/html, Size: 740 bytes --]
next reply other threads:[~2015-03-10 4:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-10 4:00 魏振伟 [this message]
2015-03-10 8:26 ` [Qemu-devel] Ask about patching our MIPS work to Qemu main branch Markus Armbruster
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=37c8316.c54.14c01d71edf.Coremail.weizhenwei-hf@loongson.cn \
--to=weizhenwei-hf@loongson.cn \
--cc=pengfei-hf@loongson.cn \
--cc=qemu-devel@nongnu.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).