From: Razvan Cojocaru <rcojocaru@bitdefender.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
keir@xen.org, xen-devel@lists.xen.org
Subject: Re: [PATCH] xen: Disable REP MOVSD optimization if introspection is active
Date: Mon, 27 Oct 2014 15:33:44 +0200 [thread overview]
Message-ID: <544E49B8.5030204@bitdefender.com> (raw)
In-Reply-To: <544E505302000078000426E2@mail.emea.novell.com>
On 10/27/2014 03:01 PM, Jan Beulich wrote:
>>>> On 27.10.14 at 12:09, <rcojocaru@bitdefender.com> wrote:
>> If you feel that the patch is acceptable, I'll correct the description
>> when submitting V2.
>
> I think it's not unreasonable conceptually, but I somewhat doubt the
> place you put the change is the right one. For one it only covers
> "rep movs", but not "rep ins" or "rep outs", and then even non-rep
> memory access may be broken up (due to the 8 byte limit of the
> channel to qemu). For me (lacking sufficient mem-event knowledge)
> it is quite hard to tell whether your change perhaps should be near
> the actual generation of the mem-event (simply because I can't -
> without spending more time than I have for this - right now see
> where exactly that event gets generated). Perhaps
> hvmemul_virtual_to_linear() should be made force *reps to 1 in
> that case instead of making various functions return failure?
Thank you, that's certainly a more elegant way to handle it than my
hack. I'll test it with reps set to 1 in hvmemul_virtual_to_linear(),
and if all goes well and there are no objections to this way of handling
it, will submit a new patch.
Thanks,
Razvan
prev parent reply other threads:[~2014-10-27 13:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 10:37 [PATCH] xen: Disable REP MOVSD optimization if introspection is active Razvan Cojocaru
2014-10-27 10:50 ` Andrew Cooper
2014-10-27 11:09 ` Razvan Cojocaru
2014-10-27 11:14 ` Andrew Cooper
2014-10-27 13:01 ` Jan Beulich
2014-10-27 13:33 ` Razvan Cojocaru [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=544E49B8.5030204@bitdefender.com \
--to=rcojocaru@bitdefender.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=keir@xen.org \
--cc=xen-devel@lists.xen.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.