Hi Ronith,
I think it forward declaration of the structure. that is is required because the below function uses that structure as parameter.0 machine_kexec.c 50 void machine_kexec_cleanup(struct kimage *image)
1 machine_kexec.c 54 static void kexec_info(struct kimage *image)
2 machine_kexec.c 73 void machine_kexec(struct kimage *image)
On Wed, Jun 15, 2016 at 9:30 PM, <kernelnewbies-request@xxxxxxxxxxxxxxxxx> wrote:
Send Kernelnewbies mailing list submissions to
kernelnewbies@xxxxxxxxxxxxxxxxx
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
or, via email, send a message with subject or body 'help' to
kernelnewbies-request@xxxxxxxxxxxxxxxxx
You can reach the person managing the list at
kernelnewbies-owner@xxxxxxxxxxxxxxxxx
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Kernelnewbies digest..."
Today's Topics:
1. Re: Identifying whether a pci device is x1, x4, x8 or x16
(John Chludzinski)
2. Call Trace analysis doubt (Muni Sekhar)
3. kimage structure (Ronit Halder)
----------------------------------------------------------------------
Message: 1
Date: Tue, 14 Jun 2016 17:46:13 -0400
From: John Chludzinski <john.chludzinski@xxxxxxxxxxx>
Subject: Re: Identifying whether a pci device is x1, x4, x8 or x16
To: Kevin Wilson <wkevils@xxxxxxxxx>
Cc: kernelnewbies@xxxxxxxxxxxxxxxxx
Message-ID: <a1bd4a3fa6f9ca7ae1b8ab7ae0cf288e@xxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Try: lshw
On 2016-06-14 08:40, Kevin Wilson wrote:
> Hi all,
> Is there a way to find out whether a PCI device in a given Linux
> machine is x1, x4, x8 or x16, in terms
> of physical dimensions (without opening the box...)
>
> Regards,
> Kevin
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies@xxxxxxxxxxxxxxxxx
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
------------------------------
Message: 2
Date: Wed, 15 Jun 2016 11:56:35 +0530
From: Muni Sekhar <munisekharrms@xxxxxxxxx>
Subject: Call Trace analysis doubt
To: kernelnewbies@xxxxxxxxxxxxxxxxx
Message-ID:
<CAHhAz+hvVefKi+h7j_eed5DrKPkQKeF3aphnSyxcxEoUqMMG+A@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset=UTF-8
Hi,
Let?s assume WARNING message says something like:
[ 0.000000] Call Trace:
[ 0.000000] [<ffffffff81762590>] dump_stack+0x45/0x56
[ 0.000000] [<ffffffff8106dd2d>] warn_slowpath_common+0x7d/0xa0
[ 0.000000] [<ffffffff8106dde4>] warn_slowpath_fmt_taint+0x44/0x50
[ 0.000000] [<ffffffff8143329c>] ? acpi_tb_acquire_table+0x3e/0x6c
[ 0.000000] [<ffffffff81765070>] warn_invalid_dmar+0x81/0x93
[ 0.000000] [<ffffffff81d8989d>] detect_intel_iommu+0xe9/0x172
[ 0.000000] [<ffffffff81d3c84f>] pci_iommu_alloc+0x4a/0x6c
[ 0.000000] [<ffffffff81d4cb4b>] mem_init+0x17/0x9c
[ 0.000000] [<ffffffff81d31e80>] start_kernel+0x23b/0x47d
[ 0.000000] [<ffffffff81d31a4e>] ? set_init_arg+0x53/0x53
[ 0.000000] [<ffffffff81d31120>] ? early_idt_handlers+0x120/0x120
[ 0.000000] [<ffffffff81d315ee>] x86_64_start_reservations+0x2a/0x2c
[ 0.000000] [<ffffffff81d31733>] x86_64_start_kernel+0x143/0x152
[ 0.000000] ---[ end trace c32c0e307381ad8a ]---
Few symbols in the above mentioned call trace are prefixed with ???
(for e.g. ?early_idt_handlers\? set_init_arg\?
acpi_tb_acquire_table), what does it mean?
Does it needs to be considered while debugging the kernel module?
Call Trace shows ?function+0xoffset/0xlength?. Does the
0xoffset/0xlength changes if the module is built with ?g option and
without ?g option?
Thanks in Advance,
--
Thanks,
Sekhar
------------------------------
Message: 3
Date: Wed, 15 Jun 2016 04:43:27 -0400
From: Ronit Halder <ronit.crj@xxxxxxxxx>
Subject: kimage structure
To: kernelnewbies <kernelnewbies@xxxxxxxxxxxxxxxxx>
Message-ID:
<CAAm8cU7-FJrg0Z3-DoR0bwzoH0az8+oFZmPBWY8d4C5nKUKoPw@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset=UTF-8
Hi,
There is a member in "struct kimage" called "entry" in kexec.h.
What does entry represents?
regards,
Ronit
------------------------------
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@xxxxxxxxxxxxxxxxx
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
End of Kernelnewbies Digest, Vol 67, Issue 13
*********************************************
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@xxxxxxxxxxxxxxxxx http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
