All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexandru Stefan ISAILA <aisaila@bitdefender.com>
To: "rcojocaru@bitdefender.com" <rcojocaru@bitdefender.com>,
	"JBeulich@suse.com" <JBeulich@suse.com>
Cc: "George.Dunlap@eu.citrix.com" <George.Dunlap@eu.citrix.com>,
	"andrew.cooper3@citrix.com" <andrew.cooper3@citrix.com>,
	"tamas@tklengyel.com" <tamas@tklengyel.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH v1 1/2] x86/mm: Add mem access rights to NPT
Date: Wed, 30 May 2018 11:20:09 +0000	[thread overview]
Message-ID: <1527679210.25123.20.camel@bitdefender.com> (raw)
In-Reply-To: <5B0E744002000078001C6E56@prv1-mh.provo.novell.com>

On Mi, 2018-05-30 at 03:52 -0600, Jan Beulich wrote:
> >
> > >
> > > >
> > > > On 30.05.18 at 11:04, <aisaila@bitdefender.com> wrote:
> > Sorry for the misunderstanding, I wanted to clarify if the 59:56
> > bits
> > are fully ok to be used or if not then where should I use 4 bits to
> > store the mem access info?
> I thought I had sufficiently explained this - you have two options:
> 1) Make sure (via some prereq patch(es)) bit 59 has no other use, and
>    then use 59:56.
> 2) Use another range that's provably having no other use, e.g.
>    58:55.
I've checked and bits 40:52 are defined in asm/page.h for page flags.
I've tried bits 53:56 and there where some problems with the guest not
starting or the image freezing, bits 62 and 63 are not free so 59:56 is
the only space to be used for this purpose and is seems to function
correctly. Is there any test I should run?

Thanks,
Alex


________________________
This email was scanned by Bitdefender
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2018-05-30 11:20 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-11 11:11 [PATCH v1 1/2] x86/mm: Add mem access rights to NPT Alexandru Isaila
2018-05-11 11:11 ` [PATCH v1 2/2] hvm/svm: Enable EMUL_UNIMPLEMENTED events on svm Alexandru Isaila
2018-05-14 17:56   ` Tamas K Lengyel
2018-05-18 15:32   ` Jan Beulich
2018-05-18 16:00     ` Tamas K Lengyel
2018-05-18 18:22       ` Razvan Cojocaru
2018-07-02 10:59   ` Jan Beulich
2018-07-02 11:29     ` Alexandru Stefan ISAILA
2018-07-05 13:35   ` Jan Beulich
2018-05-18 15:30 ` [PATCH v1 1/2] x86/mm: Add mem access rights to NPT Jan Beulich
2018-05-18 18:30   ` Razvan Cojocaru
2018-05-22  9:49     ` Jan Beulich
2018-05-22 13:35       ` Alexandru Stefan ISAILA
2018-05-22 13:44         ` Jan Beulich
2018-05-30  9:04           ` Alexandru Stefan ISAILA
2018-05-30  9:52             ` Jan Beulich
2018-05-30 11:20               ` Alexandru Stefan ISAILA [this message]
2018-05-30 11:29                 ` Jan Beulich
2018-05-30 13:56                   ` Andrew Cooper
2018-06-05 14:45                     ` Alexandru Stefan ISAILA
2018-06-05 15:38                       ` Jan Beulich

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=1527679210.25123.20.camel@bitdefender.com \
    --to=aisaila@bitdefender.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=rcojocaru@bitdefender.com \
    --cc=tamas@tklengyel.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.