All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Olivier B." <xen.list@daevel.fr>
To: xen-devel@lists.xensource.com
Subject: Re: [PATCH] Re: tmem on 4.1 (was Re: Freeze schedule)
Date: Thu, 20 Jan 2011 10:13:11 +0100	[thread overview]
Message-ID: <4D37FCA7.40402@daevel.fr> (raw)
In-Reply-To: <1295511813.14981.4653.camel@zakaz.uk.xensource.com>

Le 20/01/2011 09:23, Ian Campbell a écrit :
> On Thu, 2011-01-20 at 08:07 +0000, Olivier B. wrote:
>> Well, it is present but disabled in the new Debian Squeeze kernel...
> Do you really mean the kernel (i.e. Linux) or do you really mean the
> hypervisor?
>
> I was not aware of any tmem support (disabled or otherwise) in the
> Debian Squeeze Linux _kernel_. It hasn't been deliberately patched in
> and it does not appear to be in the xen.git snapshot used in the Xen
> dom0 flavour of the kernel.
>
> You are right that it is present and disabled in the Squeeze hypervisor
> -- this is simply the default in the Xen 4.0.1 release and hasn't been
> tweaked by Debian.
>
> Ian.
>

I don't know, on a Squeeze Dom0 with "tmem" parameters on default 
hypervisor and kernel, I have that :

root! yunze:~# xm tmem-list -a
G=Tt:39,Te:0,Cf:0,Af:0,Pf:0,Ta:0,Lm:0,Et:0,Ea:0,Rt:0,Ra:0,Rx:0,Fp:0
T=Gn:0,Gt:0,Gx:0,Gm:2147483647,Pn:0,Pt:0,Px:0,Pm:2147483647,gn:0,gt:0,gx:0,gm:2147483647,pn:0,pt:0,px:0,pm:2147483647,Fn:0,Ft:0,Fx:0,Fm:2147483647,On:0,Ot:0,Ox:0,Om:2147483647,Cn:0,Ct:0,Cx:0,Cm:2147483647,cn:0,ct:0,cx:0,cm:2147483647,dn:0,dt:0,dx:0,dm:2147483647


Is it "suffisant" to say that it works ?

but :
root! yunze:~# xm list 9
Name                                        ID   Mem VCPUs      State   
Time(s)
rome                                         9   512     2     
-b----     11.8
root! yunze:~# xm tmem-list 9
-1

and from the VM :
root! rome:~# cat /proc/cmdline
root=/dev/mapper/vg--rome-root ro rootflags=data=writeback rootdelay=1 
panic=60 swiotlb=force iommu=soft tmem
root! rome:~# uname -a
Linux rome 2.6.32-5-xen-amd64 #1 SMP Wed Jan 12 05:46:49 UTC 2011 x86_64 
GNU/Linux

But as I was saying, this is difficult to find any documentation, so I 
really don't know what is wrong or not...

Olivier

  reply	other threads:[~2011-01-20  9:13 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-11 17:14 Freeze schedule Ian Jackson
2011-01-11 18:28 ` Ian Jackson
2011-01-11 19:43   ` Ian Jackson
2011-01-12  8:11     ` Jan Beulich
2011-01-12  8:36       ` Keir Fraser
2011-01-12 11:29         ` Ian Jackson
2011-01-12 11:33           ` Keir Fraser
2011-01-12  8:14   ` tmem on 4.1 (was Re: Freeze schedule) Jan Beulich
2011-01-12 18:32     ` Dan Magenheimer
     [not found]       ` <4D2ECA37020000780002C2B9@vpn.id2.novell.com20110119165349.GF8286@whitby.uk.xensource.com>
2011-01-13  8:47       ` Jan Beulich
2011-01-19 16:53         ` [PATCH] " Tim Deegan
2011-01-19 21:38           ` Dan Magenheimer
2011-01-19 21:51             ` Sander Eikelenboom
2011-01-20  7:17             ` Keir Fraser
2011-01-20  8:07               ` Olivier B.
2011-01-20  8:23                 ` Ian Campbell
2011-01-20  9:13                   ` Olivier B. [this message]
2011-01-20 10:04               ` Jan Beulich
2011-01-20 10:18                 ` Ian Campbell
2011-01-21 17:32               ` Ian Jackson
2011-01-20  9:31             ` Tim Deegan
2011-01-20 22:49               ` Dan Magenheimer

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=4D37FCA7.40402@daevel.fr \
    --to=xen.list@daevel.fr \
    --cc=xen-devel@lists.xensource.com \
    /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.