From: Tamas K Lengyel <tamas@tklengyel.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Alexandru Isaila <aisaila@bitdefender.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Razvan Cojocaru <rcojocaru@bitdefender.com>,
Xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH v2] x86/mm: Add mem access rights to NPT
Date: Fri, 29 Jun 2018 10:42:40 -0600 [thread overview]
Message-ID: <CABfawhmYHQy36bbQ_du0yHjbfNHwmoL=oDY+EX5COJeZA64SBg@mail.gmail.com> (raw)
In-Reply-To: <5B35FE1C02000078001CF056@prv1-mh.provo.novell.com>
On Fri, Jun 29, 2018 at 3:38 AM Jan Beulich <JBeulich@suse.com> wrote:
>
> >>> On 29.06.18 at 10:42, <aisaila@bitdefender.com> wrote:
> > I've started a win 7 machine with no introspection or xen-access. After
> > 30 min of uptime there were 0 inserts into the tree. I guess the
> > overhead is down to a minimum with no user modified access rights.
>
> Thanks, this is helpful to know. In that case though, as said before, I'd
> like to ask to defer setting up of the radix tree to the point where it
> actually is going to be needed.
Are you worried about the radix tree being present (ie radix_tree_init
have been called) before it is used for mem_access? As I said earlier,
a lookup on an empty radix tree is equivalent of a NULL check. I don't
get how not having the tree initialized will be any faster then doing
a lookup on an empty one.
Tamas
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-06-29 16:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-18 15:17 [PATCH v2] x86/mm: Add mem access rights to NPT Alexandru Isaila
2018-06-18 15:39 ` Tamas K Lengyel
2018-06-19 8:14 ` Alexandru Stefan ISAILA
2018-06-19 14:22 ` Tamas K Lengyel
2018-06-22 15:51 ` Jan Beulich
2018-06-28 14:10 ` Alexandru Stefan ISAILA
2018-06-28 14:40 ` Jan Beulich
2018-06-28 14:53 ` Alexandru Stefan ISAILA
2018-06-28 14:58 ` Razvan Cojocaru
2018-06-29 6:17 ` Jan Beulich
2018-06-29 6:13 ` Jan Beulich
2018-06-29 8:42 ` Alexandru Stefan ISAILA
2018-06-29 9:38 ` Jan Beulich
2018-06-29 16:42 ` Tamas K Lengyel [this message]
2018-07-02 6:37 ` Jan Beulich
2018-07-02 8:01 ` Alexandru Stefan ISAILA
2018-07-02 8:20 ` Jan Beulich
2018-06-28 16:29 ` Tamas K Lengyel
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='CABfawhmYHQy36bbQ_du0yHjbfNHwmoL=oDY+EX5COJeZA64SBg@mail.gmail.com' \
--to=tamas@tklengyel.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=aisaila@bitdefender.com \
--cc=andrew.cooper3@citrix.com \
--cc=rcojocaru@bitdefender.com \
--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.