From: "Carsten Schiers" <carsten@schiers.de>
To: "Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>
Cc: "Sander Eikelenboom" <linux@eikelenboom.it>,
xen-devel <xen-devel@lists.xensource.com>,
"Jan Beulich" <jbeulich@suse.com>,
"Konrad Rzeszutek Wilk" <konrad@darnok.org>
Subject: Re: Load increase after memory upgrade (part2)
Date: Wed, 29 Feb 2012 13:56:09 +0100 [thread overview]
Message-ID: <zarafa.4f4e2069.413c.75dd1c180ec000b7@uhura.space.zz> (raw)
In-Reply-To: <zarafa.4f4e15b5.3926.5c7b11b715fbc27d@uhura.space.zz>
[-- Attachment #1.1: Type: text/plain, Size: 6280 bytes --]
I am very sorry. I accidently started the DomU with the wrong config file, thus it's clear why there is no difference
between the two. And unfortunately, the DomU with the correct config file is having a BUG:
[ 14.674883] BUG: unable to handle kernel paging request at ffffc7fffffff000
[ 14.674910] IP: [<ffffffff811b4c0b>] swiotlb_bounce+0x2e/0x31
[ 14.674930] PGD 0
[ 14.674940] Oops: 0002 [#1] SMP
[ 14.674952] CPU 0
[ 14.674957] Modules linked in: nfsd exportfs nfs lockd fscache auth_rpcgss nfs_acl sunrpc tda10023 budget_av evdev saa7146_vv videodev v4l2_compat_ioctl32 videobuf_dma_sg videobuf_core budget_core snd_pcm dvb_core snd_timer saa7146 snd ttpci_eeprom soundcore snd_page_alloc i2c_core pcspkr ext3 jbd mbcache xen_netfront xen_blkfront
[ 14.675057]
[ 14.675065] Pid: 0, comm: swapper/0 Not tainted 3.2.8-amd64 #1
[ 14.675079] RIP: e030:[<ffffffff811b4c0b>] [<ffffffff811b4c0b>] swiotlb_bounce+0x2e/0x31
[ 14.675097] RSP: e02b:ffff880013fabe58 EFLAGS: 00010202
[ 14.675106] RAX: ffff880012800000 RBX: 0000000000000001 RCX: 0000000000001000
[ 14.675116] RDX: 0000000000001000 RSI: ffff880012800000 RDI: ffffc7fffffff000
[ 14.675126] RBP: 0000000000000002 R08: ffffc7fffffff000 R09: ffff880013f98000
[ 14.675137] R10: 0000000000000001 R11: ffff880003376000 R12: ffff8800032c5090
[ 14.675147] R13: 0000000000000149 R14: ffff8800033e0000 R15: ffffffff81601fd8
[ 14.675163] FS: 00007f3ff9893700(0000) GS:ffff880013fa8000(0000) knlGS:0000000000000000
[ 14.675175] CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b
[ 14.675184] CR2: ffffc7fffffff000 CR3: 0000000012683000 CR4: 0000000000000660
[ 14.675195] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 14.675205] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[ 14.675216] Process swapper/0 (pid: 0, threadinfo ffffffff81600000, task ffffffff8160d020)
[ 14.675227] Stack:
[ 14.675232] ffffffff81211826 ffff880002eda000 0000000000000000 ffffc90000408000
[ 14.675251] 00000000000b0150 0000000000000006 ffffffffa013ec4a ffffffff810946cd
[ 14.675270] ffffffff81099203 ffff880003376000 0000000000000000 ffff880002eda4b0
[ 14.675289] Call Trace:
[ 14.675295] <IRQ>
[ 14.675307] [<ffffffff81211826>] ? xen_swiotlb_sync_sg_for_cpu+0x2e/0x47
[ 14.675322] [<ffffffffa013ec4a>] ? vpeirq+0x7f/0x198 [budget_core]
[ 14.675337] [<ffffffff810946cd>] ? handle_irq_event_percpu+0x166/0x184
[ 14.675350] [<ffffffff81099203>] ? __rcu_process_callbacks+0x71/0x2f8
[ 14.675364] [<ffffffff8104d175>] ? tasklet_action+0x76/0xc5
[ 14.675376] [<ffffffff8120a9ac>] ? eoi_pirq+0x5b/0x77
[ 14.675388] [<ffffffff8104cbc6>] ? __do_softirq+0xc4/0x1a0
[ 14.675400] [<ffffffff8120a022>] ? __xen_evtchn_do_upcall+0x1c7/0x205
[ 14.675412] [<ffffffff8134b06c>] ? call_softirq+0x1c/0x30
[ 14.675425] [<ffffffff8100fa47>] ? do_softirq+0x3f/0x79
[ 14.675436] [<ffffffff8104c996>] ? irq_exit+0x44/0xb5
[ 14.675452] [<ffffffff8120b032>] ? xen_evtchn_do_upcall+0x27/0x32
[ 14.675464] [<ffffffff8134b0be>] ? xen_do_hypervisor_callback+0x1e/0x30
[ 14.675473] <EOI>
Complete log is attached.
BR, Carsten.
-----Ursprüngliche Nachricht-----
An:Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>;
CC:Konrad Rzeszutek Wilk <konrad@darnok.org>; xen-devel <xen-devel@lists.xensource.com>; Jan Beulich <jbeulich@suse.com>; Sander Eikelenboom <linux@eikelenboom.it>;
Von:Carsten Schiers <carsten@schiers.de>
Gesendet:Mi 29.02.2012 13:16
Betreff:Re: [Xen-devel] Load increase after memory upgrade (part2)
Anlage:inline.txt
Great news: it works and load is back to normal. In the attached graph you can see the peak
in blue (compilation of the patched 3.2.8 Kernel) and then after 16.00 the going life of the
video DomU. We are below an avaerage of 7% usage (figures are in Permille).
Thanks so much. Is that already "the final patch"?
BR, Carsten.
-----Ursprüngliche Nachricht-----
An:Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>;
CC:Sander Eikelenboom <linux@eikelenboom.it>; xen-devel <xen-devel@lists.xensource.com>; Jan Beulich <jbeulich@suse.com>; Konrad Rzeszutek Wilk <konrad@darnok.org>;
Von:Carsten Schiers <carsten@schiers.de>
Gesendet:Di 28.02.2012 15:39
Betreff:Re: [Xen-devel] Load increase after memory upgrade (part2)
Anlage:inline.txt
Well let me check for a longer period of time, and especially, whether the DomU is still
working (can do that only from at home), but load looks pretty well after applying the
patch to 3.2.8 :-D.
BR,
Carsten.
-----Ursprüngliche Nachricht-----
An:Jan Beulich <JBeulich@suse.com>;
CC:Konrad Rzeszutek Wilk <konrad@darnok.org>; xen-devel <xen-devel@lists.xensource.com>; Carsten Schiers <carsten@schiers.de>; Sander Eikelenboom <linux@eikelenboom.it>;
Von:Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Gesendet:Fr 17.02.2012 16:18
Betreff:Re: [Xen-devel] Load increase after memory upgrade (part2)
On Thu, Feb 16, 2012 at 08:56:53AM +0000, Jan Beulich wrote:
> >>> On 15.02.12 at 20:28, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:
> >@@ -1550,7 +1552,11 @@ static void *__vmalloc_area_node(struct vm_struct *area, gfp_t gfp_mask,
> > struct page **pages;
> > unsigned int nr_pages, array_size, i;
> > gfp_t nested_gfp = (gfp_mask & GFP_RECLAIM_MASK) | __GFP_ZERO;
> >-
> >+gfp_t dma_mask = gfp_mask & (__GFP_DMA | __GFP_DMA32);
> >+if (xen_pv_domain()) {
> >+if (dma_mask == (__GFP_DMA | __GFP_DMA32))
>
> I didn't spot where you force this normally invalid combination, without
> which the change won't affect vmalloc32() in a 32-bit kernel.
>
> >+gfp_mask &= (__GFP_DMA | __GFP_DMA32);
>
> gfp_mask &= ~(__GFP_DMA | __GFP_DMA32);
>
> Jan
Duh!
Good eyes. Thanks for catching that.
>
> >+}
> > nr_pages = (area->size - PAGE_SIZE) >> PAGE_SHIFT;
> > array_size = (nr_pages * sizeof(struct page *));
> >
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
[-- Attachment #1.2: Type: text/html, Size: 34028 bytes --]
[-- Attachment #2: debug.log --]
[-- Type: application/octet-stream, Size: 21410 bytes --]
[-- Attachment #3: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2012-02-29 12:56 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-24 12:28 Load increase after memory upgrade (part2) Carsten Schiers
2011-11-25 18:42 ` Konrad Rzeszutek Wilk
2011-11-25 22:11 ` Carsten Schiers
2011-11-28 15:28 ` Konrad Rzeszutek Wilk
2011-11-28 15:40 ` Ian Campbell
2011-11-28 16:45 ` Konrad Rzeszutek Wilk
2011-11-29 8:31 ` Jan Beulich
2011-11-29 9:31 ` Carsten Schiers
2011-11-29 9:46 ` Carsten Schiers
2011-11-29 10:23 ` Ian Campbell
2011-11-29 15:33 ` Konrad Rzeszutek Wilk
2011-12-02 15:23 ` Konrad Rzeszutek Wilk
2011-12-04 11:59 ` Carsten Schiers
2011-12-04 12:09 ` Carsten Schiers
2011-12-06 3:26 ` Konrad Rzeszutek Wilk
2011-12-14 20:23 ` Konrad Rzeszutek Wilk
2011-12-14 22:07 ` Konrad Rzeszutek Wilk
2011-12-15 14:52 ` Carsten Schiers
2011-12-16 14:56 ` Carsten Schiers
2011-12-16 15:04 ` Konrad Rzeszutek Wilk
2011-12-16 15:51 ` Carsten Schiers
2011-12-16 16:19 ` Konrad Rzeszutek Wilk
2011-12-17 22:12 ` Carsten Schiers
2011-12-18 0:19 ` Sander Eikelenboom
2011-12-19 14:56 ` Konrad Rzeszutek Wilk
2012-01-10 21:55 ` Konrad Rzeszutek Wilk
2012-01-12 22:06 ` Sander Eikelenboom
2012-01-13 8:12 ` Jan Beulich
2012-01-13 15:13 ` Konrad Rzeszutek Wilk
2012-01-15 11:32 ` Sander Eikelenboom
2012-01-17 21:02 ` Konrad Rzeszutek Wilk
2012-01-18 11:28 ` Pasi Kärkkäinen
2012-01-18 11:39 ` Jan Beulich
2012-01-18 11:35 ` Jan Beulich
2012-01-18 14:29 ` Konrad Rzeszutek Wilk
2012-01-23 22:32 ` Konrad Rzeszutek Wilk
2012-01-24 8:58 ` Jan Beulich
2012-01-24 14:17 ` Konrad Rzeszutek Wilk
2012-01-24 21:32 ` Carsten Schiers
2012-01-25 12:02 ` Carsten Schiers
2012-01-25 19:06 ` Carsten Schiers
2012-01-25 21:02 ` Konrad Rzeszutek Wilk
2012-02-15 19:28 ` Konrad Rzeszutek Wilk
2012-02-16 8:56 ` Jan Beulich
2012-02-17 15:07 ` Konrad Rzeszutek Wilk
2012-02-28 14:35 ` Carsten Schiers
2012-02-29 12:10 ` Carsten Schiers
2012-02-29 12:56 ` Carsten Schiers [this message]
2012-05-11 9:39 ` Carsten Schiers
2012-05-11 19:41 ` Konrad Rzeszutek Wilk
2012-06-13 16:55 ` Konrad Rzeszutek Wilk
2012-06-14 7:07 ` Jan Beulich
2012-06-14 18:33 ` Konrad Rzeszutek Wilk
2012-06-14 18:43 ` Carsten Schiers
2012-06-14 8:38 ` David Vrabel
2012-06-14 18:31 ` Konrad Rzeszutek Wilk
2012-06-14 18:40 ` Carsten Schiers
2012-06-14 19:16 ` Carsten Schiers
2011-12-19 14:54 ` Konrad Rzeszutek Wilk
2011-12-04 12:18 ` Carsten Schiers
2011-11-28 16:58 ` Laszlo Ersek
2011-11-29 9:37 ` Carsten Schiers
2011-11-28 15:52 ` Carsten Schiers
2011-11-26 9:14 ` Carsten Schiers
2011-11-28 15:30 ` Konrad Rzeszutek Wilk
2011-11-29 9:42 ` Carsten Schiers
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=zarafa.4f4e2069.413c.75dd1c180ec000b7@uhura.space.zz \
--to=carsten@schiers.de \
--cc=jbeulich@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=konrad@darnok.org \
--cc=linux@eikelenboom.it \
--cc=xen-devel@lists.xensource.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;
as well as URLs for NNTP newsgroup(s).