From: Zhongze Liu <blackskygg@gmail.com>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
Julien Grall <julien.grall@arm.com>,
"andrew.cooper3@citrix.com" <andrew.cooper3@citrix.com>,
Lars Kurth <lars.kurth@citrix.com>
Subject: Re: [GSoC]about the task "Share a page in memory from the VM config file"
Date: Thu, 23 Mar 2017 08:13:41 +0800 [thread overview]
Message-ID: <CAHrd_jrgSf8ztk2sNZ9PxHC0V-L4mLg-F5oBU3kpfP3VMLfnTw@mail.gmail.com> (raw)
In-Reply-To: <CAHrd_jphaUSqHyYYkrF+UZMNyv79Ln1dSX5ymjmKbvNQaa1C5A@mail.gmail.com>
Back to the GSoC task.
Do I need to meet any special hardware requirements to complete the task?
Currently I have 12G RAM and 128G SSD + 1T HDD.
The output of "lscpu" on my test machine is as follows:
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 4
On-line CPU(s) list: 0-3
Thread(s) per core: 1
Core(s) per socket: 4
Socket(s): 1
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 94
Model name: Intel(R) Core(TM) i5-6300HQ CPU @ 2.30GHz
Stepping: 3
CPU MHz: 800.030
CPU max MHz: 3200.0000
CPU min MHz: 800.0000
BogoMIPS: 4609.00
Virtualization: VT-x
L1d cache: 32K
L1i cache: 32K
L2 cache: 256K
L3 cache: 6144K
NUMA node0 CPU(s): 0-3
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep
mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht
tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs
bts rep_good nopl xtopology nonstop_tsc aperfmperf tsc_known_freq pni
pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr
pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes
xsave avx f16c rdrand lahf_lm abm 3dnowprefetch epb intel_pt
tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle
avx2 smep bmi2 erms invpcid rtm mpx rdseed adx smap clflushopt
xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify
hwp_act_window hwp_epp
Cheers.
Zhongze Liu.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-03-23 0:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-01 11:54 [GSoC]about the task "Share a page in memory from the VM config file" Sky Liu
2017-03-01 19:36 ` Stefano Stabellini
2017-03-03 17:13 ` Sky Liu
2017-03-03 19:25 ` Stefano Stabellini
2017-03-05 4:58 ` Sky Liu
2017-03-23 0:13 ` Zhongze Liu [this message]
2017-03-23 1:00 ` Stefano Stabellini
2017-03-28 17:36 ` Stefano Stabellini
2017-03-29 0:15 ` Stefano Stabellini
2017-03-30 1:07 ` Zhongze Liu
2017-03-30 2:33 ` Zhongze Liu
2017-03-30 17:52 ` Stefano Stabellini
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=CAHrd_jrgSf8ztk2sNZ9PxHC0V-L4mLg-F5oBU3kpfP3VMLfnTw@mail.gmail.com \
--to=blackskygg@gmail.com \
--cc=andrew.cooper3@citrix.com \
--cc=julien.grall@arm.com \
--cc=lars.kurth@citrix.com \
--cc=sstabellini@kernel.org \
--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 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).