qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Lionel Landwerlin <lionel.landwerlin@openwide.fr>
To: Shin-ichiro KAWASAKI <kawasaki@juno.dti.ne.jp>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] sh : performance problem
Date: Sun, 01 Mar 2009 18:39:42 +0100	[thread overview]
Message-ID: <1235929182.7364.17.camel@coalu.atr> (raw)
In-Reply-To: <49AAB377.8050809@juno.dti.ne.jp>

Le lundi 02 mars 2009 à 01:10 +0900, Shin-ichiro KAWASAKI a écrit :
> Lionel Landwerlin wrote:
> > Le dimanche 01 mars 2009 à 15:05 +0900, Shin-ichiro KAWASAKI a écrit :
> >> Hi, Lionel.
> >> Thank you for the response!
> >>
> >> Lionel Landwerlin wrote:
> >>> Le vendredi 27 février 2009 à 01:28 +0900, Shin-ichiro KAWASAKI a
> >>> écrit :
> >>>
> >>> Hi Shin-ichiro,
> >>>
> >>> I'm interested by your patch, but it does not apply on top of the r6215
> >>> (qemu svn) + qemu-sh patches
> >>> ( http://git.kernel.org/?p=virt/qemu/lethal/qemu-sh.git;a=summary) 
> >>>
> >>> Should I try on the last qemu svn ?
> >> Yes.  When I send patch to qemu-devel ml, I make diff against
> >> qemu main repository.  Could you try on it?
> > 
> > Yes, I will.
> > 
> > Do you know when the qemu-sh patches will be integrated to qemu ?
> 
> Nope.
> 
> Sometimes the main developers afford some time for sh kindly, then
> some of the patches in the qemu-sh staging repository are already
> integrated.  But some patches are left. I guess they are busy on
> other CPU archs.
> 
> Especially, it's not a good time to apply patches which is not so
> serious, because version cutting work is going now.
> 
> Regards,
> Shin-ichiro KAWASAKI
> 
> 

There is also one thing that is annoying me.

With the algorithm you proposed in your patch, you're not able anymore
to raise the MMU_ITLB_MULTIPLE and MMU_DTLB_MULTIPLE exceptions. This
makes the MMU emulation different from the real processor (even if
thoses cases aren't even handled in Linux and probably others OS).

For example you can probably not map the same physical area with
differents virtual page sizes.

-- 
Lionel Landwerlin <lionel.landwerlin@openwide.fr>

  reply	other threads:[~2009-03-01 17:39 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-26 16:28 [Qemu-devel] sh : performance problem Shin-ichiro KAWASAKI
2009-02-28 19:15 ` Lionel Landwerlin
2009-03-01  6:05   ` Shin-ichiro KAWASAKI
2009-03-01 12:46     ` Lionel Landwerlin
2009-03-01 16:10       ` Shin-ichiro KAWASAKI
2009-03-01 17:39         ` Lionel Landwerlin [this message]
2009-03-02 14:46           ` Shin-ichiro KAWASAKI
2009-03-02 22:30     ` Lionel Landwerlin
2009-03-03 15:32       ` Shin-ichiro KAWASAKI
2009-03-02 23:58 ` Lionel Landwerlin
2009-03-03  0:09   ` Lionel Landwerlin
2009-03-03 15:46   ` Shin-ichiro KAWASAKI
2009-03-03 18:57     ` Lionel Landwerlin
2009-03-03 19:25       ` Laurent Desnogues
2009-03-03 22:28         ` Lionel Landwerlin
2009-03-04  2:59           ` Paul Brook
2009-03-04 15:22             ` Shin-ichiro KAWASAKI
2009-03-04 15:39           ` Shin-ichiro KAWASAKI
2009-03-03 23:11     ` Lionel Landwerlin
2009-03-04 15:12       ` Shin-ichiro KAWASAKI

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=1235929182.7364.17.camel@coalu.atr \
    --to=lionel.landwerlin@openwide.fr \
    --cc=kawasaki@juno.dti.ne.jp \
    --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).