All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@suse.com>
To: aisaila@bitdefender.com
Cc: Tamas K Lengyel <tamas@tklengyel.com>,
	Wei Liu <wei.liu2@citrix.com>,
	Razvan Cojocaru <rcojocaru@bitdefender.com>,
	George Dunlap <George.Dunlap@eu.citrix.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	xen-devel <xen-devel@lists.xenproject.org>,
	Roger Pau Monne <roger.pau@citrix.com>
Subject: Re: [PATCH v3 2/3] x86/mm: Introduce altp2m_set_entry_by_page_order
Date: Thu, 02 May 2019 08:46:31 -0600	[thread overview]
Message-ID: <5CCB02C7020000780022B53C@prv1-mh.provo.novell.com> (raw)
In-Reply-To: <20190409120324.13940-2-aisaila@bitdefender.com>

>>> On 09.04.19 at 14:03, <aisaila@bitdefender.com> wrote:
> --- a/xen/arch/x86/mm/mem_access.c
> +++ b/xen/arch/x86/mm/mem_access.c
> @@ -279,7 +279,7 @@ int p2m_set_altp2m_mem_access(struct domain *d, struct p2m_domain *hp2m,
>          gfn_t gfn2 = _gfn(gfn_l & mask);
>          mfn_t mfn2 = _mfn(mfn_x(mfn) & mask);
>  
> -        /* Note: currently it is not safe to remap to a shared entry */
> +	/* Note: currently it is not safe to remap to a shared entry */

Stray and bad (hard tab) change. But you've been meaning
to re-send this anyway.

Jan



_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

WARNING: multiple messages have this Message-ID (diff)
From: "Jan Beulich" <JBeulich@suse.com>
To: <aisaila@bitdefender.com>
Cc: Tamas K Lengyel <tamas@tklengyel.com>,
	Wei Liu <wei.liu2@citrix.com>,
	Razvan Cojocaru <rcojocaru@bitdefender.com>,
	George Dunlap <George.Dunlap@eu.citrix.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	xen-devel <xen-devel@lists.xenproject.org>,
	Roger Pau Monne <roger.pau@citrix.com>
Subject: Re: [Xen-devel] [PATCH v3 2/3] x86/mm: Introduce altp2m_set_entry_by_page_order
Date: Thu, 02 May 2019 08:46:31 -0600	[thread overview]
Message-ID: <5CCB02C7020000780022B53C@prv1-mh.provo.novell.com> (raw)
Message-ID: <20190502144631.A6k_O6WZjzDEzP69JirQjGgjNockXJmLkiBi-kK73cA@z> (raw)
In-Reply-To: <20190409120324.13940-2-aisaila@bitdefender.com>

>>> On 09.04.19 at 14:03, <aisaila@bitdefender.com> wrote:
> --- a/xen/arch/x86/mm/mem_access.c
> +++ b/xen/arch/x86/mm/mem_access.c
> @@ -279,7 +279,7 @@ int p2m_set_altp2m_mem_access(struct domain *d, struct p2m_domain *hp2m,
>          gfn_t gfn2 = _gfn(gfn_l & mask);
>          mfn_t mfn2 = _mfn(mfn_x(mfn) & mask);
>  
> -        /* Note: currently it is not safe to remap to a shared entry */
> +	/* Note: currently it is not safe to remap to a shared entry */

Stray and bad (hard tab) change. But you've been meaning
to re-send this anyway.

Jan



_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  parent reply	other threads:[~2019-05-02 14:46 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-09 12:03 [PATCH v3 1/3] x86/mm: Introduce altp2m_get_gfn_type_access Alexandru Stefan ISAILA
2019-04-09 12:03 ` [Xen-devel] " Alexandru Stefan ISAILA
2019-04-09 12:03 ` [PATCH v3 2/3] x86/mm: Introduce altp2m_set_entry_by_page_order Alexandru Stefan ISAILA
2019-04-09 12:03   ` [Xen-devel] " Alexandru Stefan ISAILA
2019-04-09 13:44   ` Tamas K Lengyel
2019-04-09 13:44     ` [Xen-devel] " Tamas K Lengyel
2019-04-10 14:18   ` George Dunlap
2019-04-10 14:18     ` [Xen-devel] " George Dunlap
2019-04-10 14:22     ` Alexandru Stefan ISAILA
2019-04-10 14:22       ` [Xen-devel] " Alexandru Stefan ISAILA
2019-05-02 14:46   ` Jan Beulich [this message]
2019-05-02 14:46     ` Jan Beulich
2019-04-09 12:04 ` [PATCH v3 3/3] x86/mm: Fix p2m_set_suppress_ve Alexandru Stefan ISAILA
2019-04-09 12:04   ` [Xen-devel] " Alexandru Stefan ISAILA
2019-04-09 13:48 ` [PATCH v3 1/3] x86/mm: Introduce altp2m_get_gfn_type_access Tamas K Lengyel
2019-04-09 13:48   ` [Xen-devel] " Tamas K Lengyel
2019-04-09 14:03   ` Alexandru Stefan ISAILA
2019-04-09 14:03     ` [Xen-devel] " Alexandru Stefan ISAILA
2019-04-09 14:37     ` Tamas K Lengyel
2019-04-09 14:37       ` [Xen-devel] " Tamas K Lengyel
2019-04-09 14:48       ` Alexandru Stefan ISAILA
2019-04-09 14:48         ` [Xen-devel] " Alexandru Stefan ISAILA
2019-04-09 15:26         ` Tamas K Lengyel
2019-04-09 15:26           ` [Xen-devel] " Tamas K Lengyel
2019-04-09 15:37           ` Alexandru Stefan ISAILA
2019-04-09 15:37             ` [Xen-devel] " Alexandru Stefan ISAILA
2019-04-10 16:02 ` George Dunlap
2019-04-10 16:02   ` [Xen-devel] " George Dunlap
2019-04-11 12:17   ` Alexandru Stefan ISAILA
2019-04-11 12:17     ` [Xen-devel] " Alexandru Stefan ISAILA
2019-04-11 12:50     ` George Dunlap
2019-04-11 12:50       ` [Xen-devel] " George Dunlap
2019-04-11 13:28       ` Tamas K Lengyel
2019-04-11 13:28         ` [Xen-devel] " Tamas K Lengyel
2019-04-12 10:59         ` Alexandru Stefan ISAILA
2019-04-12 10:59           ` [Xen-devel] " Alexandru Stefan ISAILA
2019-05-02 14:43 ` Jan Beulich
2019-05-02 14:43   ` [Xen-devel] " 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=5CCB02C7020000780022B53C@prv1-mh.provo.novell.com \
    --to=jbeulich@suse.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=aisaila@bitdefender.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=rcojocaru@bitdefender.com \
    --cc=roger.pau@citrix.com \
    --cc=tamas@tklengyel.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.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.