public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Terence Ripperda <tripperda@nvidia.com>
Cc: Dave Jones <davej@redhat.com>, Andi Kleen <ak@suse.de>,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC] Cachemap for 2.6.12rc4-mm1.  Was Re: [PATCH] enhance x86 MTRR handling
Date: Thu, 19 May 2005 00:03:56 +0200	[thread overview]
Message-ID: <20050518220356.GC1250@wotan.suse.de> (raw)
In-Reply-To: <20050518220120.GJ2596@hygelac>

> I have no doubts that this isn't in ready condition yet. at the last
> time I was working on this, I remember I was comparing how it behaved
> on various systems at my disposal and there were some glaring problems
> I was trying to take notes on. I think they were cachemap api
> problems, but I don't recall the details. I'll try to review the
> current code and old email to remember.

I plan to do more work in this area in the future too.

> 
> right now I think there were a lot of excessive printouts for
> debugging purposes. I also have no doubts that there are coding style
> differences that need to be cleaned up (feel free to tell me when my code
> sucks or isn't up to style).

Perhaps should concentrate on the basic design first.

> 
> on a side note, last I was working on this I still had to keep an
> extra tree around and manually diff things, which is a burden and easy
> to goof things up. is there an easier way to do this? it looks like
> you guys are experimenting with git, is there an faq on how to get
> started with that?

I use quilt (http://quilt.sourceforge.net) for keeping patchkits.
Works well. It is not a real SCM, but can be combined with one.

-Andi


  reply	other threads:[~2005-05-18 22:05 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-12  9:08 [PATCH] enhance x86 MTRR handling Jan Beulich
2005-05-12 16:18 ` Dave Jones
2005-05-12 17:02   ` David Addison
2005-05-12 21:41   ` [RFC] Cachemap for 2.6.12rc4-mm1. Was " Dave Jones
2005-05-13 13:29     ` Andi Kleen
2005-05-13 14:24       ` Dave Hansen
2005-05-13 14:35         ` Andi Kleen
2005-05-13 15:52       ` Dave Jones
2005-05-18 22:01         ` Terence Ripperda
2005-05-18 22:03           ` Andi Kleen [this message]
2005-05-18 22:15             ` Terence Ripperda
2005-05-18 22:42               ` Andi Kleen
2005-05-19  3:57             ` Randy Dunlap
2005-05-13 22:40     ` H. Peter Anvin
2005-05-13 23:23       ` Dave Jones
2005-05-13 23:36         ` H. Peter Anvin
2005-05-13 23:42           ` Dave Jones
2005-05-13 23:49             ` H. Peter Anvin

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=20050518220356.GC1250@wotan.suse.de \
    --to=ak@suse.de \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tripperda@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox