From: Oren Twaig <oren@scalemp.com>
To: Anthony Iliopoulos <anthony.iliopoulos@huawei.com>,
Dave Hansen <dave@sr71.net>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Shay Goikhman <shay.goikhman@huawei.com>,
Paul Mundt <paul.mundt@huawei.com>,
Carlos Villavieja <villavieja@hps.utexas.edu>,
Nacho Navarro <nacho.navarro@bsc.es>,
Avi Mendelson <avi.mendelson@tce.technion.ac.il>,
Yoav Etsion <yetsion@tce.technion.ac.il>,
Gerald Schaefer <gerald.schaefer@de.ibm.com>,
David Gibson <david@gibson.dropbear.id.au>,
linux-arch <linux-arch@vger.kernel.org>
Subject: Re: [PATCH] x86, hugetlb: add missing TLB page invalidation for hugetlb_cow()
Date: Thu, 15 May 2014 10:05:05 +0300 [thread overview]
Message-ID: <53746721.6060408@scalemp.com> (raw)
In-Reply-To: <20140515170035.GA15779@server-36.huawei.corp>
On 05/15/2014 08:00 PM, Anthony Iliopoulos wrote:
> I have dismissed this case, since I assume that there are many more
> cycles spent in servicing the TLB invalidation IPI, walking the pgtable
> plus other related overhead (e.g. sched) than in updating the pte/pmd
> so I am not sure how possible it would be to hit this condition.
Hi Anthony,
I have a question about the above statement. What will happen with multi
cpu VMs ? won't the race described above can happen ? I.e one virtual CPU
can will visit the host and the other will continue to encounter your race ?
Thanks,
Oren.
next prev parent reply other threads:[~2014-05-15 7:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140514092948.GA17391@server-36.huawei.corp>
2014-05-13 22:44 ` [PATCH] x86, hugetlb: add missing TLB page invalidation for hugetlb_cow() Dave Hansen
2014-05-15 17:00 ` Anthony Iliopoulos
2014-05-14 17:24 ` Dave Hansen
2014-05-15 7:05 ` Oren Twaig [this message]
2014-05-15 7:05 ` Oren Twaig
2014-05-17 9:24 ` Anthony Iliopoulos
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=53746721.6060408@scalemp.com \
--to=oren@scalemp.com \
--cc=anthony.iliopoulos@huawei.com \
--cc=avi.mendelson@tce.technion.ac.il \
--cc=dave@sr71.net \
--cc=david@gibson.dropbear.id.au \
--cc=gerald.schaefer@de.ibm.com \
--cc=hpa@zytor.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nacho.navarro@bsc.es \
--cc=paul.mundt@huawei.com \
--cc=shay.goikhman@huawei.com \
--cc=tglx@linutronix.de \
--cc=villavieja@hps.utexas.edu \
--cc=x86@kernel.org \
--cc=yetsion@tce.technion.ac.il \
/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).