qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Khansa Butt <khansa@kics.edu.pk>
To: "Andreas Färber" <andreas.faerber@web.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEMU development for MIPS64 user mode
Date: Sat, 9 Apr 2011 15:51:15 +0500	[thread overview]
Message-ID: <BANLkTi=85BjxuHXiq125BUJ-GWkeXnfReQ@mail.gmail.com> (raw)
In-Reply-To: <37559859-44A6-4DC2-AE65-9383EB1C8D55@web.de>

[-- Attachment #1: Type: text/plain, Size: 2694 bytes --]

Please see inline comments highlighted in red.

On Wed, Mar 30, 2011 at 12:04 AM, Andreas Färber <andreas.faerber@web.de>wrote:

> Hi,
>
> Am 29.03.2011 um 08:49 schrieb Khansa Butt:
>
>
>  I have added support for MIPS64 user mode emulation in QEMU and email git
>> patch to the qemu-devel mailing list
>> but I got no any response yet. My Patch mail has the following subject
>> line
>> MIPS64 user mode emulation Patch
>> please verify that this patch mail is not neglected or guide me towards
>> the proper way of patch submitting.
>>
>
> You should use git-send-email to submit it (marking it as [PATCH]) so that
> it can be applied with git-am, see
> http://wiki.qemu.org/Contribute/SubmitAPatch and the list archives.
> Also don't forget to cc the maintainer(s) - Aurelien for mips and Riku for
> linux-user IIRC.
>
> A description of how to test it may be helpful. Maybe you have links to
> mips64 binaries that work?
>
> Usually, the subject line of the commit message is prefixed with the topic
> (linux-user) or architecture (mips).
> If all the people you name contributed to this patch, you should probably
> add their SoBs before yours.
> The patch is rather large - is it possible to split it up into a patch
> series with at least a linux-user and a (target-)mips part?
>
> TARGET_OCTEON looks rather uncommon to me...
>
> Your patch contains a "Nasty hack". Please elaborate on that - what's the
> problem, do you intend to fix it later, etc.
>
>
linux-user/mips64/syscall.h
+/* Nasty hack: define a fake errno value for use by sigreturn.  */
+#define TARGET_QEMU_ESIGRETURN 255
+
The above lines has been copied from linux-user/mips32/syscall.h, in order
to define the constant TARGET_QEMU_ESIGRETURN(as it is needed in
main.c:cpu_loop())


> You simply comment out a #warning that signal handling is not implemented
> for mipsn64. Why didn't you implement it? Don't you need it?
>

The signal handling for Mips64 is same as for other architectures.  qemu
handles signals which comes from a program and actual handling is done by
host operating system. we follow the same convention. why this warning is
generated initially?



> Similarly you comment out a sign extension. Please elaborate. If it's a bug
> and definitely wrong, it should be moved to its own patch, explaining what
> goes wrong and fully removing it instead.
>
>
resolved this sign extension problem


> In CPUMIPSState, the surrounding struct members use lowercase characters.
>
> Some spaces missing after if.
>
> Thanks for your contribution and for taking the time to go through the
> review process.
>
> Regards,
> Andreas
>

[-- Attachment #2: Type: text/html, Size: 4183 bytes --]

      reply	other threads:[~2011-04-09 10:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-29  6:49 [Qemu-devel] QEMU development for MIPS64 user mode Khansa Butt
2011-03-29 19:04 ` Andreas Färber
2011-04-09 10:51   ` Khansa Butt [this message]

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='BANLkTi=85BjxuHXiq125BUJ-GWkeXnfReQ@mail.gmail.com' \
    --to=khansa@kics.edu.pk \
    --cc=andreas.faerber@web.de \
    --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).