From: Christian Borntraeger <borntraeger@de.ibm.com>
To: kvm-devel@lists.sourceforge.net
Cc: Laurent Vivier <Laurent.Vivier@bull.net>,
Ingo Molnar <mingo@elte.hu>,
linux-kernel <linux-kernel@vger.kernel.org>,
virtualization <virtualization@lists.linux-foundation.org>
Subject: Re: [kvm-devel] [PATCH 2/4] Introduce a new fields "gtime" and "cgtime" in task_struct and signal_struct
Date: Mon, 20 Aug 2007 15:52:57 +0200 [thread overview]
Message-ID: <200708201552.57617.borntraeger@de.ibm.com> (raw)
In-Reply-To: <46C99392.3050205@bull.net>
Am Montag, 20. August 2007 schrieb Laurent Vivier:
> Index: kvm/fs/proc/array.c
> ===================================================================
> --- kvm.orig/fs/proc/array.c 2007-08-20 11:11:30.000000000 +0200
> +++ kvm/fs/proc/array.c 2007-08-20 13:04:03.000000000 +0200
Just a heads up, this patch collides with this fix in mm:
http://marc.info/?l=linux-mm-commits&m=118737949222362&w=2
If Ingo accepts this fix, your patch should be adopted in array.c to use
cputime_t for gtime as well. Lets see what Ingo thinks.
Christian
WARNING: multiple messages have this Message-ID (diff)
From: Christian Borntraeger <borntraeger-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>
To: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Cc: Laurent Vivier <Laurent.Vivier-6ktuUTfB/bM@public.gmane.org>,
linux-kernel
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
virtualization
<virtualization-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>
Subject: Re: [PATCH 2/4] Introduce a new fields "gtime" and "cgtime" in task_struct and signal_struct
Date: Mon, 20 Aug 2007 15:52:57 +0200 [thread overview]
Message-ID: <200708201552.57617.borntraeger@de.ibm.com> (raw)
In-Reply-To: <46C99392.3050205-6ktuUTfB/bM@public.gmane.org>
Am Montag, 20. August 2007 schrieb Laurent Vivier:
> Index: kvm/fs/proc/array.c
> ===================================================================
> --- kvm.orig/fs/proc/array.c 2007-08-20 11:11:30.000000000 +0200
> +++ kvm/fs/proc/array.c 2007-08-20 13:04:03.000000000 +0200
Just a heads up, this patch collides with this fix in mm:
http://marc.info/?l=linux-mm-commits&m=118737949222362&w=2
If Ingo accepts this fix, your patch should be adopted in array.c to use
cputime_t for gtime as well. Lets see what Ingo thinks.
Christian
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next prev parent reply other threads:[~2007-08-20 13:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-20 13:13 [PATCH 2/4] Introduce a new fields "gtime" and "cgtime" in task_struct and signal_struct Laurent Vivier
2007-08-20 13:13 ` Laurent Vivier
2007-08-20 13:52 ` Christian Borntraeger [this message]
2007-08-20 13:52 ` Christian Borntraeger
2007-08-20 14:17 ` [kvm-devel] " Laurent Vivier
2007-08-20 14:17 ` Laurent Vivier
2007-08-20 14:17 ` Laurent Vivier
2007-08-20 13:52 ` [kvm-devel] " Christian Borntraeger
2009-08-05 6:59 ` Ingo Molnar
2009-08-05 6:59 ` Ingo Molnar
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=200708201552.57617.borntraeger@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=Laurent.Vivier@bull.net \
--cc=kvm-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=virtualization@lists.linux-foundation.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.