diff for duplicates of <92EBB4272BF81E4089A7126EC1E7B2846677E3E1@IRSMSX101.ger.corp.intel.com>
diff --git a/a/content_digest b/N1/content_digest
index 81e9742..e2b3008 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -44,20 +44,20 @@
"To\0'Bjorn Helgaas' <helgaas\@kernel.org>\0"
]
[
- "Cc\0Rajat Jain <rajatxjain\@gmail.com>",
- " Myron Stowe <myron.stowe\@redhat.com>",
+ "Cc\0Bjorn Helgaas <bhelgaas\@google.com>",
+ " Sinan Kaya <okaya\@codeaurora.org>",
+ " Rajat Jain <rajatja\@google.com>",
+ " Rajat Jain <rajatxjain\@gmail.com>",
" David Daney <david.daney\@cavium.com>",
" linux-pci\@vger.kernel.org <linux-pci\@vger.kernel.org>",
" Timur Tabi <timur\@codeaurora.org>",
" linux-kernel\@vger.kernel.org <linux-kernel\@vger.kernel.org>",
- " Sinan Kaya <okaya\@codeaurora.org>",
" Julia Lawall <Julia.Lawall\@lip6.fr>",
" linux-arm-msm <linux-arm-msm\@vger.kernel.org>",
- " Bjorn Helgaas <bhelgaas\@google.com>",
- " Rajat Jain <rajatja\@google.com>",
" Yinghai Lu <yinghai\@kernel.org>",
" Shawn Lin <shawn.lin\@rock-chips.com>",
- " linux-arm <linux-arm-kernel\@lists.infradead.org>\0"
+ " linux-arm <linux-arm-kernel\@lists.infradead.org>",
+ " Myron Stowe <myron.stowe\@redhat.com>\0"
]
[
"\0000:1\0"
@@ -221,4 +221,4 @@
"Commercial Register: Amtsgericht Muenchen HRB 186928"
]
-2da6b8f805a2f1aa770e1fe2377d2e44e4b528aaa418f97bdb7c75a061cfc11d
+b758f6114e78996af2597e1da85ce12ad5b9012ed815567d158f4803f4be560c
diff --git a/a/1.txt b/N2/1.txt
index 21076f5..3d78d00 100644
--- a/a/1.txt
+++ b/N2/1.txt
@@ -1,32 +1,41 @@
Hi Bjorn
-Thanks a lot for your reply and explanations. Sorry for my late reply due to some other emergencies.
+Thanks a lot for your reply and explanations. Sorry for my late reply due t=
+o some other emergencies.
>
>On Tue, May 02, 2017 at 12:02:53PM +0000, Patel, Mayurkumar wrote:
>> >On Fri, Apr 21, 2017 at 2:46 AM, Patel, Mayurkumar
>> ><mayurkumar.patel@intel.com> wrote:
>> >>>On 4/17/2017 12:38 PM, Bjorn Helgaas wrote:
->> >>>>> Like you said, what do we do by default is the question. Should we opt
+>> >>>>> Like you said, what do we do by default is the question. Should we=
+ opt
>> >>>>> for safe like we are doing, or try to save some power.
->> >>>> I think safety is paramount. Every user should be able to boot safely
->> >>>> without any kernel parameters. We don't want users to have a problem
+>> >>>> I think safety is paramount. Every user should be able to boot saf=
+ely
+>> >>>> without any kernel parameters. We don't want users to have a probl=
+em
>> >>>> booting and then have to search for a workaround like booting with
->> >>>> "pcie_aspm=off". Most users will never do that.
+>> >>>> "pcie_aspm=3Doff". Most users will never do that.
>> >>>
>> >>>OK, no problem with leaving the behavior as it is.
>> >>>
->> >>>My initial approach was #2. We knew this way that user had full control
+>> >>>My initial approach was #2. We knew this way that user had full contr=
+ol
>> >>>over the ASPM policy by changing the BIOS option. Then, Mayurkumar
->> >>>complained that ASPM is not enabled following a hotplug insertion to an
->> >>>empty slot. That's when I switched to #3 as it sounded like a good thing
+>> >>>complained that ASPM is not enabled following a hotplug insertion to =
+an
+>> >>>empty slot. That's when I switched to #3 as it sounded like a good th=
+ing
>> >>>to have for us.
>> >>>
>> >>>> Here's a long-term strawman proposal, see what you think:
>> >>>>
->> >>>> - Deprecate CONFIG_PCIEASPM_DEFAULT, CONFIG_PCIEASPM_POWERSAVE, etc.
+>> >>>> - Deprecate CONFIG_PCIEASPM_DEFAULT, CONFIG_PCIEASPM_POWERSAVE, e=
+tc.
>> >>>> - Default aspm_policy is POLICY_DEFAULT always.
->> >>>> - POLICY_DEFAULT means Linux doesn't touch anything: if BIOS enabled
+>> >>>> - POLICY_DEFAULT means Linux doesn't touch anything: if BIOS enab=
+led
>> >>>> ASPM, we leave it that way; we leave ASPM disabled on hot-added
>> >>>> devices.
>> >>>
@@ -63,8 +72,10 @@ Thanks a lot for your reply and explanations. Sorry for my late reply due to som
>
BIOS that I am having, has an SMI handler Which gets triggered upon
-Hotplug (Data Link Layer State Changed) Interrupt Which configures ASPM L1/L1SS in BIOS
-and We are still using Native Hotplug driver. Sounds like BIOS we have in our System,
+Hotplug (Data Link Layer State Changed) Interrupt Which configures ASPM L1/=
+L1SS in BIOS
+and We are still using Native Hotplug driver. Sounds like BIOS we have in o=
+ur System,
does not inform OS that it wants control ASPM.
>> >> I am seeing already following problem(or may be influence) with
diff --git a/a/content_digest b/N2/content_digest
index 81e9742..7a9b027 100644
--- a/a/content_digest
+++ b/N2/content_digest
@@ -44,20 +44,20 @@
"To\0'Bjorn Helgaas' <helgaas\@kernel.org>\0"
]
[
- "Cc\0Rajat Jain <rajatxjain\@gmail.com>",
- " Myron Stowe <myron.stowe\@redhat.com>",
+ "Cc\0Bjorn Helgaas <bhelgaas\@google.com>",
+ " Sinan Kaya <okaya\@codeaurora.org>",
+ " Rajat Jain <rajatja\@google.com>",
+ " Rajat Jain <rajatxjain\@gmail.com>",
" David Daney <david.daney\@cavium.com>",
" linux-pci\@vger.kernel.org <linux-pci\@vger.kernel.org>",
" Timur Tabi <timur\@codeaurora.org>",
" linux-kernel\@vger.kernel.org <linux-kernel\@vger.kernel.org>",
- " Sinan Kaya <okaya\@codeaurora.org>",
" Julia Lawall <Julia.Lawall\@lip6.fr>",
" linux-arm-msm <linux-arm-msm\@vger.kernel.org>",
- " Bjorn Helgaas <bhelgaas\@google.com>",
- " Rajat Jain <rajatja\@google.com>",
" Yinghai Lu <yinghai\@kernel.org>",
" Shawn Lin <shawn.lin\@rock-chips.com>",
- " linux-arm <linux-arm-kernel\@lists.infradead.org>\0"
+ " linux-arm <linux-arm-kernel\@lists.infradead.org>",
+ " Myron Stowe <myron.stowe\@redhat.com>\0"
]
[
"\0000:1\0"
@@ -69,32 +69,41 @@
"\n",
"Hi Bjorn\n",
"\n",
- "Thanks a lot for your reply and explanations. Sorry for my late reply due to some other emergencies.\n",
+ "Thanks a lot for your reply and explanations. Sorry for my late reply due t=\n",
+ "o some other emergencies.\n",
">\n",
">On Tue, May 02, 2017 at 12:02:53PM +0000, Patel, Mayurkumar wrote:\n",
">> >On Fri, Apr 21, 2017 at 2:46 AM, Patel, Mayurkumar\n",
">> ><mayurkumar.patel\@intel.com> wrote:\n",
">> >>>On 4/17/2017 12:38 PM, Bjorn Helgaas wrote:\n",
- ">> >>>>> Like you said, what do we do by default is the question. Should we opt\n",
+ ">> >>>>> Like you said, what do we do by default is the question. Should we=\n",
+ " opt\n",
">> >>>>> for safe like we are doing, or try to save some power.\n",
- ">> >>>> I think safety is paramount. Every user should be able to boot safely\n",
- ">> >>>> without any kernel parameters. We don't want users to have a problem\n",
+ ">> >>>> I think safety is paramount. Every user should be able to boot saf=\n",
+ "ely\n",
+ ">> >>>> without any kernel parameters. We don't want users to have a probl=\n",
+ "em\n",
">> >>>> booting and then have to search for a workaround like booting with\n",
- ">> >>>> \"pcie_aspm=off\". Most users will never do that.\n",
+ ">> >>>> \"pcie_aspm=3Doff\". Most users will never do that.\n",
">> >>>\n",
">> >>>OK, no problem with leaving the behavior as it is.\n",
">> >>>\n",
- ">> >>>My initial approach was #2. We knew this way that user had full control\n",
+ ">> >>>My initial approach was #2. We knew this way that user had full contr=\n",
+ "ol\n",
">> >>>over the ASPM policy by changing the BIOS option. Then, Mayurkumar\n",
- ">> >>>complained that ASPM is not enabled following a hotplug insertion to an\n",
- ">> >>>empty slot. That's when I switched to #3 as it sounded like a good thing\n",
+ ">> >>>complained that ASPM is not enabled following a hotplug insertion to =\n",
+ "an\n",
+ ">> >>>empty slot. That's when I switched to #3 as it sounded like a good th=\n",
+ "ing\n",
">> >>>to have for us.\n",
">> >>>\n",
">> >>>> Here's a long-term strawman proposal, see what you think:\n",
">> >>>>\n",
- ">> >>>> - Deprecate CONFIG_PCIEASPM_DEFAULT, CONFIG_PCIEASPM_POWERSAVE, etc.\n",
+ ">> >>>> - Deprecate CONFIG_PCIEASPM_DEFAULT, CONFIG_PCIEASPM_POWERSAVE, e=\n",
+ "tc.\n",
">> >>>> - Default aspm_policy is POLICY_DEFAULT always.\n",
- ">> >>>> - POLICY_DEFAULT means Linux doesn't touch anything: if BIOS enabled\n",
+ ">> >>>> - POLICY_DEFAULT means Linux doesn't touch anything: if BIOS enab=\n",
+ "led\n",
">> >>>> ASPM, we leave it that way; we leave ASPM disabled on hot-added\n",
">> >>>> devices.\n",
">> >>>\n",
@@ -131,8 +140,10 @@
">\n",
"\n",
"BIOS that I am having, has an SMI handler Which gets triggered upon\n",
- "Hotplug (Data Link Layer State Changed) Interrupt Which configures ASPM L1/L1SS in BIOS\n",
- "and We are still using Native Hotplug driver. Sounds like BIOS we have in our System,\n",
+ "Hotplug (Data Link Layer State Changed) Interrupt Which configures ASPM L1/=\n",
+ "L1SS in BIOS\n",
+ "and We are still using Native Hotplug driver. Sounds like BIOS we have in o=\n",
+ "ur System,\n",
"does not inform OS that it wants control ASPM.\n",
"\n",
">> >> I am seeing already following problem(or may be influence) with\n",
@@ -221,4 +232,4 @@
"Commercial Register: Amtsgericht Muenchen HRB 186928"
]
-2da6b8f805a2f1aa770e1fe2377d2e44e4b528aaa418f97bdb7c75a061cfc11d
+59baff146ebb954ca75037aaa21ee6336a57957e27df17d4b951b7bd73f0d245
diff --git a/a/content_digest b/N3/content_digest
index 81e9742..b2451ef 100644
--- a/a/content_digest
+++ b/N3/content_digest
@@ -32,32 +32,16 @@
"ref\00020170503211050.GA9506\@bhelgaas-glaptop.roam.corp.google.com\0"
]
[
- "From\0Patel, Mayurkumar <mayurkumar.patel\@intel.com>\0"
+ "From\0mayurkumar.patel\@intel.com (Patel, Mayurkumar)\0"
]
[
- "Subject\0RE: [PATCH V8 4/5] PCI/ASPM: save power on values during bridge init\0"
+ "Subject\0[PATCH V8 4/5] PCI/ASPM: save power on values during bridge init\0"
]
[
"Date\0Mon, 15 May 2017 09:10:17 +0000\0"
]
[
- "To\0'Bjorn Helgaas' <helgaas\@kernel.org>\0"
-]
-[
- "Cc\0Rajat Jain <rajatxjain\@gmail.com>",
- " Myron Stowe <myron.stowe\@redhat.com>",
- " David Daney <david.daney\@cavium.com>",
- " linux-pci\@vger.kernel.org <linux-pci\@vger.kernel.org>",
- " Timur Tabi <timur\@codeaurora.org>",
- " linux-kernel\@vger.kernel.org <linux-kernel\@vger.kernel.org>",
- " Sinan Kaya <okaya\@codeaurora.org>",
- " Julia Lawall <Julia.Lawall\@lip6.fr>",
- " linux-arm-msm <linux-arm-msm\@vger.kernel.org>",
- " Bjorn Helgaas <bhelgaas\@google.com>",
- " Rajat Jain <rajatja\@google.com>",
- " Yinghai Lu <yinghai\@kernel.org>",
- " Shawn Lin <shawn.lin\@rock-chips.com>",
- " linux-arm <linux-arm-kernel\@lists.infradead.org>\0"
+ "To\0linux-arm-kernel\@lists.infradead.org\0"
]
[
"\0000:1\0"
@@ -221,4 +205,4 @@
"Commercial Register: Amtsgericht Muenchen HRB 186928"
]
-2da6b8f805a2f1aa770e1fe2377d2e44e4b528aaa418f97bdb7c75a061cfc11d
+aa88b6c55996c58495a1ff841bdfb953f1102adba311a5c426f7e843b5b563dc
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.