Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752318AbbFKWjN (ORCPT ); Thu, 11 Jun 2015 18:39:13 -0400 Received: from mail-wi0-f193.google.com ([209.85.212.193]:35359 "EHLO mail-wi0-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750762AbbFKWjH (ORCPT ); Thu, 11 Jun 2015 18:39:07 -0400 MIME-Version: 1.0 In-Reply-To: References: <1433270522-1973-1-git-send-email-mcgrof@do-not-panic.com> Date: Thu, 11 Jun 2015 15:39:05 -0700 Message-ID: Subject: Re: [PATCH] ia64: remove paravirt code From: Tony Luck To: "Luis R. Rodriguez" Cc: "Yu, Fenghua" , "linux-ia64@vger.kernel.org" , Linux Kernel Mailing List , pbonzini@redhat.com, Boris Ostrovsky , Chris Wright , Jeremy Fitzhardinge , Alok Kataria , Rusty Russell Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1204 Lines: 29 On Wed, Jun 10, 2015 at 4:40 PM, Luis R. Rodriguez wrote: > Its quite a huge chunk of code removed, I doubt that .o files would > remain intact after this, but I could be wrong. I think run time > validation and examination of the code changes, understanding of the > code changes is necessary, but also likely just as run time tests. Actually it seems the most of the .o files below arch/ia64/kernel look quite similar ... some post-processing of the "objdump -d" output the squash out addreses ... and the before/after .o files have few enough differences that they can be looked at manually. > Is there no ia64 regression test suite? Not really. > I don't see ia64 getting much love anyway these days so would it not > hurt to merge and spin through linux-next for a while and if no issues > are reported make it fly in? Not sure how many people besides me are booting linux-next kernels. Still - let's give it a try, -Tony -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/