kvm-devel，欢迎阁下参观：
第二届中国西部（重庆）建筑建材及节能科技展览会
2008年3月6-8日 陈家坪 重庆展览中心
大会网址：http://www.cnfair.org
◆主题展区：
| 建筑节能玻璃及贴膜技术 | 建筑节能门窗幕墙 | 新型墙体、保温材料及砖瓦设备 |
| 干混砂浆技术产品及设备 | 节水与水资源利用 | 绿色照明，智能节电产品及技术 |
| 可再生能源建筑利用技术 | 热水节能技术产品 | 供热采暖、空调及通风技术设备 |
◆同期举办：
第五届中国西部建筑装饰及装饰材料展
第二届中国重庆园
On Thu, 14 Feb 2008 22:49:04 -0800 Christoph Lameter <[EMAIL PROTECTED]> wrote:
> These special additional callbacks are required because XPmem (and likely
> other mechanisms) do use their own rmap (multiple processes on a series
> of remote Linux instances may be accessing the memory of a process
On Thu, 14 Feb 2008 22:49:02 -0800 Christoph Lameter <[EMAIL PROTECTED]> wrote:
> Two callbacks to remove individual pages as done in rmap code
>
> invalidate_page()
>
> Called from the inner loop of rmap walks to invalidate pages.
>
> age_page()
>
> Called for the determination of
On Thu, 14 Feb 2008 22:49:00 -0800 Christoph Lameter <[EMAIL PROTECTED]> wrote:
> MMU notifiers are used for hardware and software that establishes
> external references to pages managed by the Linux kernel. These are
> page table entriews or tlb entries or something else that allows
> hardware (s
On Thu, 14 Feb 2008 22:49:01 -0800 Christoph Lameter <[EMAIL PROTECTED]> wrote:
> The invalidation of address ranges in a mm_struct needs to be
> performed when pages are removed or permissions etc change.
hm. Do they? Why? If I'm in the process of zero-copy writing a hunk of
memory out to har
On Wed, 2008-02-13 at 08:58 +0200, Avi Kivity wrote:
> It'll need to be built against your kernel tree; please provide a URL.
curl http://penguinppc.org/~hollisb/kvm/kvm-powerpc.mbox | git-am
--
Hollis Blanchard
IBM Linux Technology Center
--
> -Original Message-
> From: Christoph Lameter [mailto:[EMAIL PROTECTED]
> Sent: Friday, February 15, 2008 2:50 PM
> To: Caitlin Bestler
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED];
[EMAIL PROTECTED];
> [EMAIL PROTECTED]; kvm-devel@lists.sourceforge.net
> Subject: RE: [ofa-general] Re: Dem
On Fri, 15 Feb 2008, Caitlin Bestler wrote:
> There isn't much point in the RDMA layer subscribing to mmu
> notifications
> if the specific RDMA device will not be able to react appropriately when
> the notification occurs. I don't see how you get around needing to know
> which devices are capable
On Fri, 2008-02-15 at 23:42 +0530, Balaji Rao wrote:
> Hello all,
>
> When going through orpofile code, I noticed that boot_cpu_data was used to
> determine CPU vendor, family etc. Will this be updated on migration to a
> different Machine say, from Intel to AMD ? If not, wouldn't it cause pro
On Thu, Feb 14, 2008 at 7:08 PM, Andrey Dmitriev <[EMAIL PROTECTED]> wrote:
>
>
> If I want to stick to debian, would the best way to do this be to just
> download kvm60 source, compile the module and load it in, or does kernel
> still require upgrading (I think latest on etch is .18 not .20)
>
You
Christoph Lameter wrote
>
> > Merely mlocking pages deals with the end-to-end RDMA semantics.
> > What still needs to be addressed is how a fastpath interface
> > would dynamically pin and unpin. Yielding pins for short-term
> > suspensions (and flushing cached translations) deals with the
> > res
On Fri, 15 Feb 2008, Caitlin Bestler wrote:
> So that would mean that mlock is used by the application before it
> registers memory for direct access, and then it is up to the RDMA
> layer and the OS to negotiate actual pinning of the addresses for
> whatever duration is required.
Right.
> The
This is the guest part of kvm clock implementation
It does not do tsc-only timing, as tsc can have deltas
between cpus, and it did not seem worthy to me to keep
adjusting them.
We do use it, however, for fine-grained adjustment.
Other than that, time comes from the host.
Signed-off-by: Glauber d
I think this version addresses avi's last comments.
I'm not resending userspace since it is unchanged
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com
This is the host part of kvm clocksource implementation. As it does
not include clockevents, it is a fairly simple implementation. We
only have to register a per-vcpu area, and start writting to it periodically.
The area is binary compatible with xen, as we use the same shadow_info
structure.
Si
> -Original Message-
> From: Christoph Lameter [mailto:[EMAIL PROTECTED]
> Sent: Friday, February 15, 2008 10:46 AM
> To: Caitlin Bestler
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED];
[EMAIL PROTECTED];
> [EMAIL PROTECTED]; kvm-devel@lists.sourceforge.net
> Subject: RE: [ofa-general] Re: De
On Fri, 15 Feb 2008, Caitlin Bestler wrote:
> > What does it mean that the "application layer has to be determine what
> > pages are registered"? The application does not know which of its
> pages
> > are currently in memory. It can only force these pages to stay in
> > memory if their are mlocked
Hello all,
When going through orpofile code, I noticed that boot_cpu_data was used to
determine CPU vendor, family etc. Will this be updated on migration to a
different Machine say, from Intel to AMD ? If not, wouldn't it cause problems ?
Please clarify.
--
regards,
balaji rao
--
Christoph Lameter asked:
>
> What does it mean that the "application layer has to be determine what
> pages are registered"? The application does not know which of its
pages
> are currently in memory. It can only force these pages to stay in
> memory if their are mlocked.
>
An application that a
This allows compiling the external module against linux.git (fastcall
has finally become the default and only choice).
Signed-off-by: Andrea Arcangeli <[EMAIL PROTECTED]>
diff --git a/kernel/external-module-compat.h b/kernel/external-module-compat.h
index 5611c12..52b745c 100644
--- a/kernel/exte
On Fri, 15 Feb 2008, Alexander Graf wrote:
> On Feb 15, 2008, at 3:56 PM, Anthony Liguori wrote:
>
> >Have you tried SLES-9 or openSUSE variants of the same age? The ss issue in
> >gfxboot is only something recently introduced. Prior to that, gfxboot used
> >big real mode so your patch wouldn't
On Feb 15, 2008, at 3:56 PM, Anthony Liguori wrote:
> Alexander Graf wrote:
>> Hi,
>>
>> this issue has already been talked about previously. Gfxboot on VMX
>> is
>> broken, because it reads SS after switching from real to protected
>> mode,
>> where SS contains an invalid value, which VMX do
The announcement below may well be of interest to people involved
in KVM. oVirt is using libvirt as its mnagement API, and the current
builds use Fedora 9 + KVM to get a cutting edge virtualization
platform / technology in combination with cutting edge Linux kernels :-)
If anyone's interested, the
Alexander Graf wrote:
> Hi,
>
> this issue has already been talked about previously. Gfxboot on VMX is
> broken, because it reads SS after switching from real to protected mode,
> where SS contains an invalid value, which VMX does not allow.
> As far as I know, gfxboot is the only application that
On Feb 15, 2008, at 2:47 PM, Avi Kivity wrote:
> Alexander Graf wrote:
>> Hi,
>>
>> this issue has already been talked about previously. Gfxboot on VMX
>> is
>> broken, because it reads SS after switching from real to protected
>> mode,
>> where SS contains an invalid value, which VMX does no
Alexander Graf wrote:
> Hi,
>
> this issue has already been talked about previously. Gfxboot on VMX is
> broken, because it reads SS after switching from real to protected mode,
> where SS contains an invalid value, which VMX does not allow.
> As far as I know, gfxboot is the only application that
Hollis Blanchard wrote:
> We're having a hard time tracking down a PowerPC bug that seems to be
> related to KVM's signal handling (SIGALRM in particular), so we're
> trying to understand the overall signal handling design.
>
> It looks like the run sequence goes something like this:
> 1. qemu
Новое в бухгалтерском и налоговом учете в 2008 году.
Однодневный семинар / 29 февраля 2008 г. / Москва
1. Анализ и сравнение ПБУ 3/2006 и ПБУ 3/2000 "Учет активов и обязательств,
стоимость которых выражена в иностранной валюте".
2. Анализ договоров в условных единицах :
-- цена товара (работ,
28 matches
Mail list logo
